[wp-trac] [WordPress Trac] #36638: Detect broken URLs in the editor

WordPress Trac noreply at wordpress.org
Tue Jul 19 22:16:24 UTC 2016

#36638: Detect broken URLs in the editor
 Reporter:  iseulde                         |       Owner:  azaozz
     Type:  task (blessed)                  |      Status:  assigned
 Priority:  normal                          |   Milestone:  4.6
Component:  Editor                          |     Version:
 Severity:  normal                          |  Resolution:
 Keywords:  needs-unit-tests needs-testing  |     Focuses:  ui

Comment (by ocean90):

 Replying to [comment:28 azaozz]:

 > We return an error only when we are sure the URL is wrong: either the
 domain name cannot be resolved or it returns 404. This leaves several
 other common cases out, for example:

 IMO the current checks are enough, reliable and cover the most common
 errors. But more important, those can be fixed by users themselves.
 Producing a 400 error seems pretty hard, it's usually the result of
 sending bad data to an API service. Authentication errors should be
 ignored because the current user and their readers might have access to
 it. 5xx errors are also unlikely and these should (hopefully) only be

 > 2. Many web servers block the `WordPress` user agent for different
 reasons. We probably could use something else in the UA, but... Doesn't
 sound right.

 This is the first time I'm hearing this. :) Do you happen to know what the
 status code is? It's probably not 404.

Ticket URL: <https://core.trac.wordpress.org/ticket/36638#comment:30>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list