[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #5196 [HTTPS Everywhere: Chrome]: Translate breakage in Chrome
#5196: Translate breakage in Chrome
--------------------------------------+-------------------------------------
Reporter: pde | Owner: aaronsw
Type: defect | Status: new
Priority: blocker | Milestone:
Component: HTTPS Everywhere: Chrome | Version:
Keywords: | Parent:
Points: | Actualpoints:
--------------------------------------+-------------------------------------
Changes (by pde):
* cc: mikeperry (added)
Comment:
I'm still learning how to use the Chrome developer tools, so I'm not
supremely confident about what I'm seeing yet. However, here's what I see
in the "Network" tab (after having right-clicked in Console and enabled
"Log XMLHTTPRequests"
It seems that Chrome starts with a to POST to
http://translate.googleapis.com/translate_a/t?anno=3&client=te_lib&format=html&v=1.0&logld=v7
, but the next line in the logs is a GET to
https://translate.googleapis.com/translate_a/t?anno=3&client=te_lib&format=html&v=1.0&logld=v7
. There is a postData payload for the POST that is of course missing in
the GET.
I would be okay disabling the translate.google.com rewrite rules in order
to push a beta release out the door, if I didn't have this niggling fear
that we might be rewriting all POSTS to GETs. We should rule that
possibility out, which means finding a nice clean test case on some other
site we can look at.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5196#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs