Closed GoogleCodeExporter closed 8 years ago
Can you capture the HTTP traffic with Fiddler and share it with us?
Please do that twice, once without proxy and another one with your proxy setup.
Thanks
Original comment by ccherub...@google.com
on 5 Oct 2011 at 4:17
I have installed Fiddler now, but how can I add my C# program
(GoContactSyncMod.exe) now to the processes? I only get IE sessions displayed,
even when I select the process GoContactSync to trace, I get no Web sessions
displayed. If you want, you can try it on your own, just download the
GoContactSync sources from http://sourceforge.net/projects/googlesyncmod/
Or you guide me how I can trace the traffic from there.
Original comment by Saller....@gmail.com
on 5 Oct 2011 at 4:45
You should probably enable the decryption of HTTPS-protected traffic:
http://www.fiddler2.com/Fiddler/help/httpsdecryption.asp
Is GoContactSyncMod a tool you wrote? If not, you should ask the project owners
for support, I see the Beta version has some changes related to proxy
management:
http://sourceforge.net/projects/googlesyncmod/files/Betas/
Original comment by ccherub...@google.com
on 5 Oct 2011 at 4:51
I enabled the HTTPS protected traffic, but it didn't work also, but after
restarting Fiddler2 I was able to catch some traffic from GoContactSync, see
attached file (without proxy). Unfortunatelly I couldn't find much details in
the trace log (only 2 connects).
Please note, that GoContactSyncMod is a tool I wrote (together with some other
guys, but I am the main developer and the BETA was a trial to improve the Proxy
Settings with ContactsRequest, this week we wanted to rollout the new version
with improved proxy, it worked fine with ContactsRequest, but it didn't work
with DocumentsRequest. After testing the old workaround approach to use
System.net section in App.config, waht already worked before the BETA for
ContactsRequest, we found out, that this workaround also not works for
DocumentsRequest (I never tested it with proxy, because on my development PC I
don't have a proxy and it worked fine, but on my deployment PC I have a proxy
script and there it didn't work).
Original comment by Saller....@gmail.com
on 5 Oct 2011 at 6:53
Attachments:
It is something like a miracle, but I tested it today afternoon and now it
worked. So I think you can close this issue, I guess it is related with our
working environment, sometimes it is working, sometimes not, but it is not a
Google Data API issue.
-- CLOSED ---
Original comment by Saller....@gmail.com
on 25 Oct 2011 at 3:26
Original comment by ccherub...@google.com
on 25 Oct 2011 at 3:52
Original issue reported on code.google.com by
Saller....@gmail.com
on 5 Oct 2011 at 5:49