There's no need to rewrite existing URL Fetch calls. httplib support is just intended to make it easier to use other libraries that depend on httplib/urllib/urllib2. The HTTP referrer issue you mention has been acknowledged. I don't have any information on its status to report, but I feel your pain. :)
-- Dan On Tue, Feb 10, 2009 at 7:45 AM, jordisan <[email protected]> wrote: > > Dan, so there's no need to rewrite our URL Fetch calls to get more > performance or functionalities, is there? > > And I guess this issue is still open: > http://code.google.com/p/googleappengine/issues/detail?id=445 > Are you working on this? We need to set/unset HTTP-referer to > connect to remote APIs as Delicious or Twitter. > > Thanks. > > On Feb 10, 7:52 am, Dan Sanderson <[email protected]> wrote: > > Correct, all of the functionality and restrictions of the URL Fetch > service > > apply to the httplib interfaces. > > > > -- Dan > > > > On Mon, Feb 9, 2009 at 6:33 PM, gesteves <[email protected]> wrote: > > > > > Quick question: The docs state that "You can use the Python standard > > > libraries urllib, urllib2 or httplib to make HTTP requests. When > > > running in App Engine, these libraries perform HTTP requests using App > > > Engine's URL fetch service, which runs on Google's scalable HTTP > > > request infrastructure." > > > > > Does that mean that changing the user-agent header is still not > > > allowed, even when using one of Python's standard libraries? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
