Whatever you set the URL to, that HTTP code will be returned

Re:Whatever you set the URL to, that HTTP code will be returned by petke on Tuesday January 26, 2016 @06:28PM (#10977072)

This site was very helpful when I refractored a program from using libcurl to cpprest. I used it to make sure the sent http request headers where exactly the same.

[ Parent | on HN ]

Re:Whatever you set the URL to, that HTTP code will be returned by jjuhl on Wednesday January 27, 2016 @01:40AM (#10978629)

You could have just looked at the traffic directly with wireshark rather than trust an external site.

[ Parent | on HN ]

Re:Whatever you set the URL to, that HTTP code will be returned by petke on Thursday January 28, 2016 @12:33AM (#10986495)

I'll remember that next time. I been using fiddler to see websites http traffic which is helpful. But my programs http traffic doesn't show up there.. So ill try wireshark next time.

[ Parent | on HN ]

Re:Whatever you set the URL to, that HTTP code will be returned by nchelluri on Wednesday January 27, 2016 @04:23AM (#10979100)

I think this might not be possible for SSL/TLS traffic, without some kind of MITM.

[ Parent | on HN ]

Re:Whatever you set the URL to, that HTTP code will be returned by lisivka on Wednesday January 27, 2016 @05:51AM (#10979380)

It is possible with SSL/TLS traffice: you need to supply private key to WireShark, so it will be able to decode conversation.

[ Parent | on HN ]

Re:Whatever you set the URL to, that HTTP code will be returned by madeofpalk on Wednesday January 27, 2016 @06:40AM (#10979524)

Most dev 'MITM' proxy tools have a way to inspect HTTPS by creating a new key and adding it to your systems trust.

Charles has a fairly neat way of making it all work.

[ Parent | on HN ]