Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #7919 > unrolled thread
| Started by | Roy Smith <roy@panix.com> |
|---|---|
| First post | 2011-06-18 14:57 -0400 |
| Last post | 2011-06-18 17:45 -0400 |
| Articles | 3 — 2 participants |
Back to article view | Back to comp.lang.python
debugging https connections with urllib2? Roy Smith <roy@panix.com> - 2011-06-18 14:57 -0400
Re: debugging https connections with urllib2? Irmen de Jong <irmen.NOSPAM@xs4all.nl> - 2011-06-18 21:40 +0200
Re: debugging https connections with urllib2? Roy Smith <roy@panix.com> - 2011-06-18 17:45 -0400
| From | Roy Smith <roy@panix.com> |
|---|---|
| Date | 2011-06-18 14:57 -0400 |
| Subject | debugging https connections with urllib2? |
| Message-ID | <roy-85CE29.14573118062011@news.panix.com> |
We've got a REST call that we're making to a service provider over https using urllib2.urlopen(). Is there any way to see exactly what's getting sent and received over the network (i.e. all the HTTP headers) in plain text? Things like tcpdump and strace only have access to the encrypted data. We can't just switch to using http because the endpoint we're talking to (and don't have control over) refuses plain-text connections.
[toc] | [next] | [standalone]
| From | Irmen de Jong <irmen.NOSPAM@xs4all.nl> |
|---|---|
| Date | 2011-06-18 21:40 +0200 |
| Message-ID | <4dfcff48$0$49184$e4fe514c@news.xs4all.nl> |
| In reply to | #7919 |
On 18-6-2011 20:57, Roy Smith wrote: > We've got a REST call that we're making to a service provider over https > using urllib2.urlopen(). Is there any way to see exactly what's getting > sent and received over the network (i.e. all the HTTP headers) in plain > text? Things like tcpdump and strace only have access to the encrypted > data. > > We can't just switch to using http because the endpoint we're talking to > (and don't have control over) refuses plain-text connections. Put a proxy between the https-service endpoint and your client app. Let the proxy talk https and let your client talk http to the proxy. Irmen
[toc] | [prev] | [next] | [standalone]
| From | Roy Smith <roy@panix.com> |
|---|---|
| Date | 2011-06-18 17:45 -0400 |
| Message-ID | <roy-6FB1B8.17454118062011@news.panix.com> |
| In reply to | #7921 |
In article <4dfcff48$0$49184$e4fe514c@news.xs4all.nl>, Irmen de Jong <irmen.NOSPAM@xs4all.nl> wrote: > On 18-6-2011 20:57, Roy Smith wrote: > > We've got a REST call that we're making to a service provider over https > > using urllib2.urlopen(). Is there any way to see exactly what's getting > > sent and received over the network (i.e. all the HTTP headers) in plain > > text? > > Put a proxy between the https-service endpoint and your client app. > Let the proxy talk https and let your client talk http to the proxy. Clever. I like. Thanks.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.python
csiph-web