-
Notifications
You must be signed in to change notification settings - Fork 2k
http-proxy to apache failed. #234
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
Comments
huh, that's weird, it definitely shouldn't redirect in your browser. That would require sending back a 300 redirect and stuff, which is a little crazy, are you sure apache isn't sending back a 300 redirect? |
I am not very familiar with apache. Also I google it, and find there are same issues about this. like |
Yeah, that's what I thought. Apache is sending back a redirect, like that guy says in that thread you sent. In that thread, he did state the solution:
(indexzero also provided an example in response to that, check it out here) |
thank you, i use another ip address for apache2. So currently my problem is resolved. |
I have an apache server running on port 82.
when i request http://www.xxxx.com/a/b
it always redirect to http://www.xxxx.com:82/a/b
Because of firewall. it will failed.
why port 82 will be shown up?
The text was updated successfully, but these errors were encountered: