Middleware for handling vendor-specific $vendor-forwarded-proto -> x-forwarded-proto. - #192
Middleware for handling vendor-specific $vendor-forwarded-proto -> x-forwarded-proto.#192ioquatix wants to merge 1 commit into
$vendor-forwarded-proto -> x-forwarded-proto.#192Conversation
…`x-forwarded-proto`.
mpalmer
left a comment
There was a problem hiding this comment.
It does what it says on the tin, and the test cases seem comprehensive, so 🎉.
I do wonder if SetXForwardedProtoHeader is the right name; it's not "setting" the header so much as using an alternate source. "Naming things" being, of course, one of the hard things, I don't want to block merge on it, but if AlternateXForwardedProtoHeader, for example, were to strike you as a suitable name, I wouldn't be against changing it.
|
I would like to change the name. I outlined my thoughts here: rack/rack#2089 (comment) @tomharvey would you like to work on refining this a bit more? |
|
A generic |
|
As mentioned in rack/rack#2089 I've created a new PR here #193 and I can pick up the feedback from @mpalmer as I continue to work in that branch. |
rack/rack#2187