[wp-trac] [WordPress Trac] #14971: X-Pingback header set when no pingbacks accepted

WordPress Trac wp-trac at lists.automattic.com
Mon Sep 27 05:45:18 UTC 2010

#14971: X-Pingback header set when no pingbacks accepted
 Reporter:  niallkennedy      |       Owner:                 
     Type:  enhancement       |      Status:  new            
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Pings/Trackbacks  |     Version:                 
 Severity:  normal            |    Keywords:  has-patch      

Comment(by filosofo):

 Replying to [ticket:14971 niallkennedy]:
 > WordPress should only advertise the header when a given site has enabled
 pingbacks. Requires moving X-Pingback out of the initial headers variable
 and into a conditional.

 I'm not sure about this.  Wouldn't it be better to respond according to
 the [http://www.hixie.ch/specs/pingback/pingback#return spec] with an
 error code 49, "Access Denied"? (I have no idea what it currently does.)

 It's not that the XMLRPC server resource doesn't exist; it's that
 pingbacks aren't allowed.  Having an accurate error response would be more
 helpful for the pinging client, because then it knows that there is a
 policy preventing pingbacks and not just that it has the wrong location or
 there is a temporary resource failure.

 Also, the X-Pingback header is only one way of providing server auto-
 discovery; the other is the `<link>` HTML head element, which is baked
 into many WP themes.

Ticket URL: <http://core.trac.wordpress.org/ticket/14971#comment:1>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list