There is an active issue with urlfetch_stub.py in the SDK where the FULL
URL is being sent to the HTTP server as the path.
Question and patch posted here:
http://stackoverflow.com/questions/31195459/appengine-dev-appserver-urllib2-urlopen-issue-with-localhost-url
Basically, it's connecting like
I’ve seen this as well and submitted a support ticket. I did not find the
debugging hilarious, but it’s nice to see someone else handle things with
better humor than me.
Karl
> On Jul 6, 2015, at 10:09 PM, Josh Whelchel (Loudr) wrote:
>
>
> There is an active issue with urlfetch_stub.py
Looks like a bug was filed yesterday. I'll update the SO post to reference
this bug so hopefully more people can star it.
https://code.google.com/p/googleappengine/issues/detail?id=12123
On Monday, July 6, 2015 at 9:24:54 PM UTC-5, Karl MacMillan wrote:
>
> I’ve seen this as well and submitted
I got a confirmation this morning from support of this issue and a suggestion
that it will be fixed in a subsequent release.
Can I just ask some Googlers - how on earth did this issue slip by? This is the
second serious SDK issue I’ve seen in recent months that would have been caught
by the
This issue was so hard to find, and related to the outgoing request, I
believe a test-case would have been hard-pressed to find it.
That said, the bug is on the stub implementation of the urlfetch API - I'd
expect some request header tests as well.
*shrug*
can't catch 'em all
On Tuesday, July
> On Jul 7, 2015, at 4:18 PM, Josh Whelchel (Loudr) wrote:
>
>
> This issue was so hard to find, and related to the outgoing request, I
> believe a test-case would have been hard-pressed to find it.
>
>
>
Why? All outgoing http requests are broken as far as I can tell.
> That said, th
