Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

RFC 2616 defines header values as case insensitive, so per default we...#1259

Open
notz wants to merge 1 commit into
restlet:2.3 from
notz:rfc-2616-compliant
Open

RFC 2616 defines header values as case insensitive, so per default we... #1259
notz wants to merge 1 commit into
restlet:2.3 from
notz:rfc-2616-compliant

Conversation

@notz

@notz notz commented Mar 17, 2017

Copy link
Copy Markdown

... should read/write headers values as case insensitive

Currently only the getValues method use case insensitive per default, all other are case sensitive.

This fixes problems behind a nginx reverse proxy, where "X-Forwarded-Proto" header is set as "X-forwarded-proto" (#1191).
The X-Forwarded-For is working because it's read in restlet with getValues method.

... should read/write headers values as case insensitive
 Currently only the getValues method use case insensitive per default, all other are case sensitive.
 This fixes problems behind a nginx reverse proxy, where "X-Forwarded-Proto" header is set as "X-forwarded-proto".
 The X-Forwarded-For is working because it's read in restlet with getValues method.

Copy link
Copy Markdown
Contributor

Hi @notz , this is not so easy to change the default read option as this class is also used elsewhere.
I have to check more deeply.
I think we can make sure that the framework internally reads the header in the right way. In the cases you read the headers from your own code, is it possible for you to read using the value in the case-insensitive way?

notz commented Apr 22, 2017 via email

Copy link
Copy Markdown
Author
I know that it's used everywhere. But the problem isn't my application. It's used different in restlet and their modules. That's the correct approach to fix problem. I know it is no small fix, but shouldn't break anything because it's RFC conform.
...
On Apr 22, 2017 15:23, "Thierry Boileau" ***@***.***> wrote: Hi @notz <https://github.com/notz> , this is not so easy to change the default read option as this class is also used elsewhere. I have to check more deeply. I think we can make sure that the framework internally reads the header in the right way. In the cases you read the headers from your own code, is it possible for you to read using the value in the case-insensitive way? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1259 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAqjozsHWlmptlhfEVbJLzOcaCfP9harks5ryf9hgaJpZM4MgYAC> .

notz commented Jan 18, 2025

Copy link
Copy Markdown
Author

@jlouvel Any chance to get this into 2.6?

jlouvel commented Jan 22, 2025

Copy link
Copy Markdown
Collaborator

Hi @notz We could tackle this change in version 2.7 which along with 3.0 version will give us the opportunity to change the Restlet API and core behavior as needed, while 2,6 should stay as close as possible to 2.5 to streamline upgrades of production apps to Java 17 and Jakarta. See https://github.com/restlet/restlet-framework-java/wiki/Roadmap

notz reacted with thumbs up emoji

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /