On May 21, 2008, at 3:22 PM, ultralame wrote:
> > OK, so I found this... > > ============ > 10.3.3 302 Found > > The requested resource resides temporarily under a different URI. > Since the redirection might be altered on occasion, the client SHOULD > continue to use the Request-URI for future requests. This response is > only cacheable if indicated by a Cache-Control or Expires header > field. > > The temporary URI SHOULD be given by the Location field in the > response. Unless the request method was HEAD, the entity of the > response SHOULD contain a short hypertext note with a hyperlink to the > new URI(s). > > If the 302 status code is received in response to a request other than > GET or HEAD, the user agent MUST NOT automatically redirect the > request unless it can be confirmed by the user, since this might > change the conditions under which the request was issued. > ============ > > ??! Why would google do this on the API, knowing that we're supposed > to be making a POST request? So wget is doing the "right" thing by > changing to a GET, as a POST might be sending info somewhere > undesirable. Do I really need to code my own HTTP utility to deal > with this? Google is doing the right thing, wget is doing the wrong thing. Google has provided a method to override wget. It is posted here: http://code.google.com/support/bin/answer.py?answer=55833&topic=10360 Ray --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
