>> This is intended behaviour (but undocumented I think); whether it is >> desirable or not is a different question. >> >> IMO this is not worth fixing; and we should just document the behaviour >> for <> headers. What do you think, Zack? > >Agreed. Why is this the intended behavior? It doesn't make much sense to me. Thanks- -R