[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-users] Content-Type value is unexpectedly changed by Jetty9
|
I call it a bug.
As per servlet spec 3.0 - 3.4 Headers, getHeader() is supposed to return the original value the specified request header.
The spec doesn't imply containers can modify / upper-case / lower-case the value.
------------------
• 3.4 Headers
• A servlet can access the headers of an HTTP request through the following methods of the HttpServletRequest interface:
■ getHeader
■ getHeaders
■ getHeaderNames
The getHeader method returns a header given the name of the header. There can be multiple headers with the same name, e.g. Cache-Control headers, in an HTTP request. If there are multiple headers with the same name, the getHeader method returns the first header in the request. The getHeaders method allows access to all the header values associated with a particular header name, returning an Enumeration of String objects.
------------------
--
Yusuke Yamamoto
@yusukey
http://samuraism.com/
On 2013/07/31, at 11:29, てらだみつるつよし <terrada3@xxxxxxxxx> wrote:
> Hi.
>
> I'm in trouble about the "Content-Type" .
>
> I used a recent version Jetty, that version is 8.1.11.v20130520. Now, I'm trying to migrate my application to version 9.0.4.v20130625.
>
> In version 8, Content-Type value is not changed by Jetty.
>
> set by client : application/x-www-form-urlencoded; charset=utf-8
>
> HttpServletRequest.getHeade("Content-Type") : application/x-www-form-urlencoded; charset=utf-8
>
> But in version 9.0.4.v20130625, "Content-Type" value is changed by Jetty.
>
> set by client : application/x-www-form-urlencoded; charset=utf-8
>
> HttpServletRequest.getHeade("Content-Type") : application/x-www-form-urlencoded; charset=UTF-8
>
> A charset value is changed(utf -> UTF).
>
> I use this value to calculate a hash value for authentication mechanism.
> This changing of a Content-Type value makes difference between a value calculated in client and that in server, so authentication is failed.
>
> I cannot judge that this is a specification or a bug.
> Have anybody tips or options to avoid this charset changing?
>
> //terada-m
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users
