-
Notifications
You must be signed in to change notification settings - Fork 79
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
Problem working with Squid web proxy #35
Comments
Doing as voloko suggested, and restoring the full url as bgreenlee suggested did not result in anymore success here:
nor here - note the port number is present in the Host header for this attempt:
|
Found it... Have to have the options look as such, just as voloko suggested way-back:
I'll wrap this into a pull request, or something similar later this evening. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm having a problem going through Squid despite the changes bgreenlee suggested 3 years ago in Issue #2.
Using Twitter::JSONStream as shown at https://gist.github.com/4179836.js?file=Listen_in_on_Campfire_room.rb , I get the following results - with a little bit of annotation sprinkled in at bottom of JSONStream#send_request, and temporarily backing out the "full url" fix bgreenlee suggested, please read on:
Meanwhile, using curl, I can generate the exact same headers, and it works...
Even just advice on where or how to investigate further would be appreciated. I've been annotating twitter-stream-0.1.16 and eventmachine-1.0.0 to try and determine where these may be diverting from whatever curl is doing right. Unfortunately, I haven't found any clues after lots of trials and errors.
My next move is to switch to the pure_ruby of eventmachine, but the initial resistance I found with that suggested to me to maybe reach out for help first.
The text was updated successfully, but these errors were encountered: