News for hackers. Stuff that matters.
Re:Please drop the SOAP by mariusmg on Thursday January 27, 2011 @05:32PM (#2149826)
Try it with Fiddler.Should work fine over https.
Re:Please drop the SOAP by bmccormack on Thursday January 27, 2011 @10:21PM (#2150655)
Perhaps the fact that I was surprised that the article's author didn't immediately think of Fiddler is evidence of how exclusively I've worked with web services via .NET. Personally, I've had a great experience with SOAP from within Visual Studio. Once the service reference is established, all coding is against the strongly-typed code-generated classes. If I must, I use Fiddler to debug. My experience has been positive.
Re:Please drop the SOAP by regularfry on Thursday January 27, 2011 @05:42PM (#2149870)
No Windows boxes round these parts, or I would have. I tried WebScarab, but without the server certificate it was a lost cause (unless I missed a trick somewhere).
Re:Please drop the SOAP by lmz on Thursday January 27, 2011 @06:39PM (#2150099)
You have to generate a certificate for the proxy (WebScarab) and have the client trust it. The proxy will then act as a man-in-the-middle, presenting its own certificate to the client. See:

http://www.owasp.org/index.php/Generating_Custom_SSL_Certifi...

Re:Please drop the SOAP by regularfry on Friday January 28, 2011 @03:34AM (#2151231)
Now I know what to do if I ever find myself in that situation again. Thanks.
Re:Please drop the SOAP by nailer on Friday January 28, 2011 @06:58AM (#2151532)
Charles proxy works on OS X and Linux.
Re:Please drop the SOAP by icey on Thursday January 27, 2011 @05:58PM (#2149933)
Thanks for the fiddler tip - I also use Wireshark for most of my debugging needs and https always causes problems.
Re:Please drop the SOAP by nailer on Friday January 28, 2011 @04:19AM (#2151303)
I'm going to check fiddler out too, but I've been using Charles proxy for the same thing if you need another way to see SSL.