Skip to content

Fix changeOrigin #231

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.

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

Closed
wants to merge 2 commits into from
Closed

Fix changeOrigin #231

wants to merge 2 commits into from

Conversation

coderarity
Copy link
Contributor

This was reverted a long time ago. I don't know why, because nobody explained it. I added it back, as it seems necessary looking at #150. There seemed to be some discussion saying it was unnecessary, but note that was before it used the changeOrigin option. This shouldn't change anything for anyone not using changeOrigin. If there's a reason to not use it, please document it this time. Thanks!

@johnsheehan
Copy link

+1 would really like to see this pulled in

@coderarity coderarity mentioned this pull request Apr 18, 2012
@rklancer
Copy link

+1

I'm writing a simple Node+CouchDB backend for a client-side single-page webapp (a learning game).

One of the backend's jobs is to reverse-proxy two legacy services we provide via Apache name-based virtual hosts. Without @coderarity's patch, the name based virtual hosts will not respond. Setting X-Forwarded-For is not sufficient.

Thanks...

@abernier
Copy link

+1

2 similar comments
@subnetmarco
Copy link
Contributor

+1

@1stvamp
Copy link
Contributor

1stvamp commented Jun 9, 2012

👍

@1stvamp
Copy link
Contributor

1stvamp commented Jun 9, 2012

#247 also got 3 or 4 +1's before I closed it in favour of this one.

@adrianlee
Copy link

I would also like to see this pulled in.

@indexzero
Copy link
Member

Cherry-picked. Thanks.

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

Successfully merging this pull request may close these issues.

8 participants