|
ProxHTTPSProxy, a Proxomitron SSL Helper Program
|
|
May. 20, 2010, 04:22 AM
(This post was last modified: May. 20, 2010 04:40 AM by Graycode.)
Post: #9
|
|||
|
|||
RE: ProxHTTPSProxy, a Proxomitron SSL Helper Program
(May. 20, 2010 03:19 AM)whenever Wrote: As the statement itself explained, I get only "host_port" from "self.path". It seems like an issue. If in a browser I enter (https)example.com:443/path/more/stuff/for/page.htm and send that through a proxy, the CONNECT command nor any header will contain the requested path portion. It will be just a '/' slash and nothing about path, page, htm. It's only enough information for a proxy to build a blind-tunnel with the target server within which encrypted content would flow, and in that muck is where the actual path / page will be transmitted. Hence it seems like the 307 redirection could only always send the browser to the root of the site but not to the path / page that was desired. That level of detail is not provided with the CONNECT method, it provides no clue about what is being requested. In order to determine what is being requested the Python would have to establish the SSL hand-shakes with the browser to a sufficient state that the browser would be willing to cough up what it was wanting. That might be possible since you already have a 'proxcert.pem' that the browser would trust. Hopefully it's obvious that I don't know much about Python. |
|||
|
« Next Oldest | Next Newest »
|

Search
Member List
Calendar
Help





![[-]](images/ONi/collapse.gif)