Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement RFC 7239 (Forwarded header) #185

Closed
jmcc0nn3ll opened this issue Feb 16, 2016 · 1 comment
Closed

Implement RFC 7239 (Forwarded header) #185

jmcc0nn3ll opened this issue Feb 16, 2016 · 1 comment
Assignees
@sbordet
Labels
Enhancement Help Wanted

Comments

@jmcc0nn3ll
Copy link
Contributor

migrated from Bugzilla #461578
status ASSIGNED severity enhancement in component proxy for 9.3.x
Reported in version 9.3.0 on platform All
Assigned to: Simone Bordet

On 2015-03-06 06:59:36 -0500, Simone Bordet wrote:

http://tools.ietf.org/html/rfc7239.

Currently the proxy servlets use the old format of "X-Forwarded-*", but the new format should be there too.
@sbordet sbordet self-assigned this Feb 17, 2016
@joakime
Copy link
Contributor

joakime commented Mar 7, 2016

For those looking for Help Wanted work, this work on this should be done in the ForwardedRequestCustomizer class.

@sbordet sbordet mentioned this issue Aug 11, 2016
Closed
gregw added a commit that referenced this issue Aug 11, 2016
@gregw
Issue #185 Implement RFC 7239
b45af1a 
Also handle legacy Https headers for #834
@gregw gregw closed this as completed Aug 11, 2016
gregw added a commit that referenced this issue Aug 12, 2016
@gregw
Issue #185 Implement RFC 7239
5fefd5d 
Improved test harness
Added more configurability
Fixed SSL session and certificate bugs
@gregw gregw mentioned this issue Aug 15, 2016
Open
@bclozel bclozel mentioned this issue Dec 19, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sbordet sbordet

Labels
Enhancement Help Wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@gregw @joakime @jmcc0nn3ll @sbordet