[wp-trac] [WordPress Trac] #52011: 'The REST API encountered an unexpected result' should be a critical error

WordPress Trac noreply at wordpress.org
Sun Aug 28 20:12:27 UTC 2022


#52011: 'The REST API encountered an unexpected result' should be a critical error
-------------------------+------------------------------
 Reporter:  oglekler     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Site Health  |     Version:  5.2
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  performance
-------------------------+------------------------------
Changes (by Clorith):

 * version:   => 5.2
 * type:  defect (bug) => enhancement


Comment:

 Hmm, I'm not sure if an unexpected result should ''always'' be a critical
 issue, but I do believe that making it aware of a few more response types
 should, for example anything in the 500-range would be server errors, and
 should probably be flagged as critical, while below that may be due to
 special firewall rules and similar when performing loopback connections.

 What are your thoughts on just improving it's awareness of status codes,
 does that sound like a good initial approach to you?

 Related: #54617 which addresses the usefulness of this message response in
 the first place

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52011#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list