I tried you're two commands for tcpdump, but it was still giving me
everything I wanted to look at in hex. I'm on OS X and wireshark would
require me to install fink, ended up using Mark Liyanges tcpflow which
showed me just what I wanted to see. Apparently I just forgot to update
the method and content type on the redirect.

Thanks for your help.

Jake

On Nov 28, 6:02 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote:
> Also, some people on the Windows platform like using Fiddler for
> debugging.  Fiddler is a HTTP proxy, so it depends on the library
> you're using whether you can configure it to use a proxy:
>
> http://www.fiddlertool.com/fiddler/
>
> On Nov 28, 3:59 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote:
>
> > I generally use Wireshark/Ethereal (http://www.wireshark.org/) for
> > looking at these sorts of things.  It is available for most platforms
> > and quite easy to use.  Basically, you capture the traffic on the
> > appropriate interface (capture menu, interfaces, start), right click on
> > the appropriate HTTP packet in the display and choose 'follow TCP
> > stream'
>
> > You could also use tcpdump (as you mentioned) to capture the traffic to
> > analyze later with tcpdump,Wireshark or another tool
> > sudo tcpdump -s0 -w /usr/tmp/tcpdump.out hostwww.google.com
> > -- s0 tells tcpdump not to limit packet length
> > -- w outputs to the specified file
>
> > To capture and look at the traffic in a live view:
> > sudo tcpdump -s0 -XX -f hostwww.google.com
> > -- s0 tells tcpdump not to limit packet length
> > -- XX tells tcpdump to give hex and ascii output
>
> > Hope this helps!
>
> > Happy Coding,
> > -Ryan
>
> > On Nov 28, 3:23 pm, "Jacob" <[EMAIL PROTECTED]> wrote:
>
> > > I've been trying to buy my HTTP library doesn't give me the body for
> > > 500's. Any hints on getting snort or tcpdump to show it to me?
>
> > > On Nov 28, 5:16 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote:
>
> > > > Hi Jacob!
>
> > > > Do you have the body of the 500 response?
>
> > > > Thanks,
>
> > > > -Ryan
>
> > > > On Nov 28, 3:12 pm, "Jacob" <[EMAIL PROTECTED]> wrote:
>
> > > > > Once again the event succsessfully was added. I deleted the event, ran
> > > > > the code again with out changing a thing and received a 500 again.- 
> > > > > Hide quoted text -- Show quoted text -- Hide quoted text -- Show 
> > > > > quoted text -


--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to