> 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
-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 wron
> Just to nitpick, there is no "proper capitalisation", since the RFC says
> that headers are case-insensitive.
I know, I referred to "proper" as in what the target machine expects.
> Apart from that, I would offer the following subjective advice, in the
> form of suggestions :
> - it sounds l
> definitiv möglicherweise?
> Martin
Most likely ;), but what should the snippet tell me?
Alexander
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
n.
> Date: Mon, 8 Jun 2009 18:34:04 +0200
> From: alexander.muel...@brz.gv.at
> To: users@tomcat.apache.org
> Subject: Re: Header names lower case
>
>
> > "apparently"? Hm, in this case I'd double-check whether whatever problem
> > you're hav
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 th
> "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
Alexander Müller:
>> RFC 2616 defines field names as case-insensitive. Relying on a
>> header field's case therefore seems at least non-portable to me.
>> Maybe you should elaborate what problem you are really trying to
>> solve.
>
> For me the case wouldnt be important, but I am forwarding (bas
> The HTTP spec (HTTP/1.1, section 4.2:
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html) states that HTTP
> header field names are case-insensitive.
>
> You should not be relying on a particular caseification (?) of header
> fields.
>
> Are you just interested in what the client sent?
>
> I can't answer your question but I'm curious: why is a HTTP header
> name's case of any importance to you?
>
> RFC 2616 defines field names as case-insensitive. Relying on a header
> field's case therefore seems at least non-portable to me.
> Maybe you should elaborate what problem you are real
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander,
On 6/8/2009 4:39 AM, Alexander Müller wrote:
> I noticed the Tomcat implementation of
> HttpServletRequest.getHeaderNames() returns all header names in lower
> case. Is there any possibility to get them with their original case?
The HTTP s
Alexander Müller:
> I noticed the Tomcat implementation of
> HttpServletRequest.getHeaderNames() returns all header names in lower
> case. Is there any possibility to get them with their original case?
I can't answer your question but I'm curious: why is a HTTP header
name's case of any importanc
>> I noticed the Tomcat implementation of HttpServletRequest.getHeaderNames()
>> returns all header names in lower case. Is there any possibility to
>> get them with their original case?
>
> Want to give us a hint about the Tomcat version you're looking at?
>
> - Chuck
I noticed it on Tomcat 5
> From: Alexander Müller [mailto:alexander.muel...@brz.gv.at]
> Subject: Re: Header names lower case
>
>
> > I noticed the Tomcat implementation of HttpServletRequest.getHeaderNames()
> > returns all header names in lower case. Is there any possibility to
> > get
> Hi,
>
> I noticed the Tomcat implementation of HttpServletRequest.getHeaderNames()
> returns all header names in lower case. Is there any possibility to get them
> with their original case?
Nobody having any idea about this behaviour?
Thanks again,
Alexander
--
15 matches
Mail list logo