this thread indicating that.
If anyone is interested, the root cause seems to be a redirect (303
see other) taking place where the url being redirected to is not
encoded.A direct request to the redirect URL, with encoding,
retrieves the intended document.
Matthew
On May 5, 11:07 pm, Matt Trinneer
, Matt Trinneer matt.trinn...@gmail.com wrote:
Hello,
I can confirm that I am also encountering this issue.
Best, Matt
On May 9, 7:14 am, tijer troels...@gmail.com wrote:
To reproduce the problem go to the google-developed app
shell.appspot.com and try to login with an iphone
Hello,
I can confirm that I am also encountering this issue.
Best, Matt
On May 9, 7:14 am, tijer troels...@gmail.com wrote:
To reproduce the problem go to the google-developed app
shell.appspot.com and try to login with an iphone.
It not having an iphone then spoof the useragent to the
encode character u'\xe2' in position
2: ordinal not in range(128). It occurs when i pass russian strings as
parameter.
2009/5/4 Matt Trinneer matt.trinn...@gmail.com
To further that post...
It seems to me that URLs containing characters such as ( and ) are not
being fetched properly
Having some luck... By using urllib2 instead of urlfetch I am able to
load the same URLs on the production server without any issue. Not
really a solution per say but it gets the job done. Appreciate
everyone's feedback.
On May 5, 10:29 pm, Matt Trinneer matt.trinn...@gmail.com wrote:
Hi
To further that post...
It seems to me that URLs containing characters such as ( and ) are not
being fetched properly on the production environment. I've attempted
escaping the characters, as per RFC 3986. However the escaped url
(http://dbpedia.org/resource/Companion_%28manga%29) doesn't