#2241: webob request.copy() != request
--------------------------+-------------------------------------------------
 Reporter:  jorge.vargas  |        Owner:        
     Type:  defect        |       Status:  new   
 Priority:  normal        |    Milestone:  2.0rc1
Component:  TurboGears    |      Version:  2.0b5 
 Severity:  normal        |   Resolution:        
 Keywords:                |  
--------------------------+-------------------------------------------------
Old description:

> TODO

New description:

 After several hours after trying to figure out why each and every
 method in codemill's hg was working except push I notice that
 CONTENT_LENGTH was getting set to -1 a couple of minutes later I ran
 the following in weberror request==new_req to my surprise it returned
 false, even better request.copy()==request returns FalsE!

 While still in shock by all this I sat down and wrote 3 unit tests one
 for TG, one for pylons and one for plain webob, to my surpise all of
 them are failing! so what's wrong? how come copy doesn't copy? even if
 the webob docs say so
 http://pythonpaste.org/webob/reference.html#modifying-the-request why
 am I getting a content-lenght of -1??

 Still skeptic about this I went to the WSGIAppController and added
 +
 new_req.environ['CONTENT_LENGTH']=request.environ['CONTENT_LENGTH']

 and now i can push! anyone knows what the heck is going on??

 patch with the tests
 http://paste.chrisarndt.de/paste/dbd7e1ff954542caa647ef65d6df97cc

-- 
Ticket URL: <http://trac.turbogears.org/ticket/2241#comment:1>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to