[CherryPy] #809: POST parsing error, cherrypy gets confused with certain POST variable content.

0 views
Skip to first unread message

CherryPy

unread,
May 5, 2008, 1:35:40 AM5/5/08
to cherrypy...@googlegroups.com
#809: POST parsing error, cherrypy gets confused with certain POST variable
content.
---------------------------+------------------------------------------------
Reporter: guest | Owner: fumanchu
Type: defect | Status: new
Priority: normal | Milestone:
Component: CherryPy code | Keywords:
---------------------------+------------------------------------------------
hi,

I had a POST variable containing the text:
"""...\n\n<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" />\n\n..."""

then cherrypy will think there is a POST variable called charset.

This is on osx incase that matters.

cheers,

--
Ticket URL: <http://www.cherrypy.org/ticket/809>
CherryPy <http://www.cherrypy.org>
CherryPy - a pythonic, object-oriented HTTP framework

CherryPy

unread,
May 5, 2008, 8:48:46 PM5/5/08
to cherrypy...@googlegroups.com
#809: POST parsing error, cherrypy gets confused with certain POST variable
content.
---------------------------+------------------------------------------------
Reporter: guest | Owner: fumanchu
Type: defect | Status: new
Priority: lowest | Milestone:
Component: CherryPy code | Resolution:
Keywords: |
---------------------------+------------------------------------------------
Changes (by guest):

* priority: normal => lowest

Comment:

Hi,

please remove this bug.

I tracked the failure down to the client side library I was using - the
problem is not with cherrypy.


cheers.

CherryPy

unread,
May 6, 2008, 12:31:17 PM5/6/08
to cherrypy...@googlegroups.com
#809: POST parsing error, cherrypy gets confused with certain POST variable
content.
---------------------------+------------------------------------------------
Reporter: guest | Owner: fumanchu
Type: defect | Status: closed
Priority: lowest | Milestone:
Component: CherryPy code | Resolution: invalid
Keywords: |
---------------------------+------------------------------------------------
Changes (by fumanchu):

* resolution: => invalid
* status: new => closed
Reply all
Reply to author
Forward
0 new messages