#8765: mod_python handler requires explicit str() cast for
HttpResponse(mimetype=...)
------------------------------------+---------------------------------------
          Reporter:  semenov        |         Owner:  nobody                    
      
            Status:  new            |     Milestone:                            
      
         Component:  HTTP handling  |       Version:  SVN                       
      
        Resolution:                 |      Keywords:  mod_python content-type 
mimetype
             Stage:  Unreviewed     |     Has_patch:  1                         
      
        Needs_docs:  0              |   Needs_tests:  0                         
      
Needs_better_patch:  0              |  
------------------------------------+---------------------------------------
Changes (by mtredinnick):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 So this proposes a solution without describing the course of events that
 makes it arise. At the moment we don't do any casting there because it
 shouldn't be necessary. What normal piece of code is passing in a non-
 ASCII mimetype?

 It's probably not too harmful -- although str() is the wrong way to do it,
 for error handling reasons; plus I'll have to look up the spec to see if
 only ASCII is permitted or if octets are also allowed -- but I'd like to
 understand how this can arise in the normal course of events before doing
 that.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8765#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to