[wp-trac] [WordPress Trac] #11286: Normal User Input Causes Status 500

[WordPress Trac]

#11286: Normal User Input Causes Status 500
--------------------------+-------------------------------------------------
 Reporter:  miqrogroove   |       Owner:           
     Type:  defect (bug)  |      Status:  new      
 Priority:  normal        |   Milestone:  2.9      
Component:  Comments      |     Version:  2.8.4    
 Severity:  normal        |    Keywords:  has-patch
--------------------------+-------------------------------------------------

Comment(by nacin):

 Replying to [comment:7 miqrogroove]:
 > I will concede that anything is better than 500 at this point.  But we
 are still confusing the HTTP and HTML layers.  If the client returns a
 zero-byte string for a "required" field, then that is a completely valid
 response at the HTTP layer

 I agree, only up until the point where the script calls wp_die(). You
 shouldn't terminate a script and show a failure message yet send 200. It
 just doesn't sit right.

 > If the client returns an entity omitting form fields entirely, then in
 that case you're at least in a gray area and should use 403.

 In that case, my opinion is that a completely blank form submission it
 should send the user back to the page from whence they came, with a 200.
 No feedback there is better than unnecessary feedback. (Unnecessary -
 wp_die(). Useful feedback - inline.)

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11286#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software