query strings not passed forward through HTTPS when AlwaysMitm in effect

[elazarl]

query strings not passed forward through HTTPS when AlwaysMitm in effect

[elazarl]

Hi,

Thanks for reporting the bug. A small stupid mistake.

Can you please check if this works for you now, and let me know?

Thanks,

[fredcy]

It is working correctly for me now, passing the query-string as part of the request. Thanks.

(This is valuable to me as I'm using goproxy to watch what happens to my website when I include a bit of Javascript tracker code provided by a third party. Goproxy makes it easy to see all the new requests to tracking sites that happen as a result and makes it easy to save the results in a file. Thanks!)

P.S. I was working on a pull request to submit to you. I was thinking about submitting it anyway but since it affects the same code there is little point. You can see my repo if you're interested in how a naive goproxy user would have hacked the code.

[elazarl]

Thanks,

I'll definitely have a look tomorrow yawn.

I really appreciate your feedback, feel free to send me questions or use
cases.

On Tue, Jan 7, 2014 at 10:59 PM, Fred Yankowski [email protected]:

It is working correctly for me now, passing the query-string as part of
the request. Thanks.

(This is valuable to me as I'm using goproxy to watch what happens to my
website when I include a bit of Javascript tracker code provided by a third
party. Goproxy makes it easy to see all the new requests to tracking sites
that happen as a result and makes it easy to save the results in a file.
Thanks!)

P.S. I was working on a pull request to submit to you. I was thinking
about submitting it anyway but since it affects the same code there is
little point. You can see my repo if you're interested in how a naive
goproxy user would have hacked the code.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/30#issuecomment-31778659
.