-
Notifications
You must be signed in to change notification settings - Fork 62
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
doge.js is redirecting to original site with no injection #35
Comments
So the origin is sending a 302 through the proxy to the browser You can intercept the response and format it as http://localhost/en/ and it should work but that is beyond the point of the example. |
Is there any way you could elaborate a little more on your above comment? I'm running into the same issue and have not been able to resolve it yet. |
Hey @costolo |
It doesn't work if you browse directly to that |
I tried with the package.json from the original 2015 commit (removed "^"s in package.json). So I don't think it's a dependency problem. What's weird is that I think http://localhost:8000/en is redirecting to http://localhost:8000 which then redirects to http://nodejs.org/en |
When I set proxy target to be Has anyone had any luck solving redirects? I'm having no success with modifying responses. |
After some digging I found out I had errors in the proxy configuration, I forgot the www in host. Should look like:
|
I tried running dodge.js locally (see code below). But when I navigate to localhost:8000 I am redirected from my proxy to https://nodejs.org/en/ and there is no image injection. Did something change that would break this code or am I doing something wrong?
The text was updated successfully, but these errors were encountered: