i don't know if that is possible in your code/framework/site system...
but you can try one of the following approaches:
a) sitewise: whenever you get a HTTP >= 400, log the traffic
b) codewise: whenever you get an HTTP>=400, get the requeststream
and response stream and log it. As you need to have the requeststream,
you might need to have a temporary copy just for logging purposes which is kind
of wastefull, but should not hurt too bad...
Frank Mantek
On 9/21/06, Mark Swanson <[EMAIL PROTECTED]> wrote:
USI wrote:
> Mark,
>
> I'm an engineer from calendar and I'm looking into this issue. Do you
> have a copy of the request handy?
>
Hello Mike,
I don't have the request. Please tell me which gdata api methods I need
to use to log the request and I'll get it to you asap.
Thank you.
--
Free replacement for Exchange and Outlook (Contacts and Calendar)
http://www.ScheduleWorld.com/tg/
WebDAV: http://www.ScheduleWorld.com/sw/webDAVDir/4000.ics
VFREEBUSY: http://www.ScheduleWorld.com/sw/freebusy/4000.ifb
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
- Re: Bug report: Google fails to parse valid rrule Frank Mantek
- Re: Bug report: Google fails to parse valid rrule Mark Swanson
