-
Notifications
You must be signed in to change notification settings - Fork 75
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
Incorrect escape of url #2
Comments
Thanks, I'll try to take a look during the weekend. |
I decided to create an own CORS-enabled (reverse) proxy using NodeJS, and also host it on Heroku. Heroku is awesome :) |
This is nice, but too bad you decided to do this instead of pushing a patch to this project or submit another issue. However, a big part of open source is collaboration, not just running around to open a new project just so you can be cool. (Caveat: I've never actually successfully submitted patches to an OSS project, even though I tried ... all I've done is run around opening new projects :)) Anyway, if you could submit a pull request to WhatEverOrigin that adds COR support, that would be super cool. I'd do it myself but I'm a bit swamped with work right now. I understand it might take you some time to learn how to use play (although it's really rather simple and well documented). I opened an issue for now, might get to it soon/later. In any case, thanks for updating here! |
I'm not gifted with infinite time either, so I just left a comment with the language-agnostic implementation details. Including a response header should not be that hard, so I'll leave it up to you. |
Thanks, I'll do that. |
Was this ever fixed? I'm trying to fetch a google cache page[0], but it seems WhateverOrigin fails to escape the URL as it should. Am I doing something wrong? [0] http://webcache.googleusercontent.com/search?q=cache:news.ycombinator.com |
I'm actually not sure, it's been a while back. Sadly I don't have the time to look into it ... but pull requests are welcome! |
Bring back fixes introduced in commit 8ed8c6b.
The URL is incorrectly escaped:
?
becomes%3F
:Actual result (status key) for the first URL:
Expected result:
The text was updated successfully, but these errors were encountered: