google-code-export / appengine-devappserver2-experiment

Automatically exported from code.google.com/p/appengine-devappserver2-experiment
0 stars 0 forks source link

CherryPy contains a bug which causes devappserver2 to fail on URI paths which contain :// #69

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Create a catch-all handler for your app.
2. Start devappserver2
3. Navigate to http://localhost:8000/http://www.google.com
4. See stack trace in logs.

What is the expected output? What do you see instead?
I expect the request to succeed.
Instead, I see a 500 error and the following stack trace:

ValueError('need more than 1 value to unpack',)
Traceback (most recent call last):
  File "/Users/tyler/optimizely/out/gae-1.8.8/lib/cherrypy/cherrypy/wsgiserver/wsgiserver2.py", line 1292, in communicate
    req.parse_request()
  File "/Users/tyler/optimizely/out/gae-1.8.8/lib/cherrypy/cherrypy/wsgiserver/wsgiserver2.py", line 580, in parse_request
    success = self.read_request_line()
  File "/Users/tyler/optimizely/out/gae-1.8.8/lib/cherrypy/cherrypy/wsgiserver/wsgiserver2.py", line 643, in read_request_line
    scheme, authority, path = self.parse_request_uri(uri)
  File "/Users/tyler/optimizely/out/gae-1.8.8/lib/cherrypy/cherrypy/wsgiserver/wsgiserver2.py", line 805, in parse_request_uri
    authority, path = remainder.split(FORWARD_SLASH, 1)
ValueError: need more than 1 value to unpack

What version of the product are you using? On what operating system?
Whichever version of devappserver2 is included in the GAE SDK 1.8.8.

Please provide any additional information below.

I've already filed a bug with CherryPy here:
https://bitbucket.org/cherrypy/cherrypy/issue/1284/wsgiserver2py-breaks-on-uri-p
aths-which

old_dev_appserver.py can be used until this is resolved.

Original issue reported on code.google.com by erichigg...@gmail.com on 6 Feb 2014 at 1:30

GoogleCodeExporter commented 9 years ago
Now that old_dev_appserver.py has been fully deprecated and removed from the 
SDK, this is even more important to get resolved.

Original comment by erichigg...@gmail.com on 10 Mar 2015 at 1:14