-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alexander,
On 6/8/2009 12:34 PM, Alexander Müller wrote: >> "apparently"? Hm, in this case I'd double-check whether whatever >> problem you're having is indeed caused by the case of the header >> names. Just to make sure you're not barking at the wrong tree. If >> the receiving party is really relying on the case of header names, >> I'd ask them to fix their broken code. > > Maybe better "definitely" :) > > If I send the headers with the proper capitalisation I get through, > otherwise I am getting an error I wouldnt send the header. > Unfortunately this is one of the situations where you cant ask the > other parties to correct their code, but have to adapt by yourself > ;). Is it only certain headers that are a problem, or is it all headers? If it's only some, you could specifically code these such that they are handled with the desired capitalization, and pass everything else through. Or, if there are some rules to the capitalization requirements (like the leading character is always caps, and anything following a - is caps, like Accept-Charset instead of accept-charset), then - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkouZaMACgkQ9CaO5/Lv0PCcDwCdGIkvXcbIj8Ie6KQJGOw6/wnk JAcAn3nA06AY21ZTe300/I3fSprhln48 =Jn/H -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
