Make WordPress Core

Opened 7 years ago

Closed 7 years ago

#7324 closed enhancement (invalid)

X-Pingback header sent despite disabled xml-rpc interface and trackbacks/pingbacks

Reported by: TobiasBg Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.6
Component: XML-RPC Keywords: x-pingback, header, xml-rpc, trackback, pingback
Focuses: Cc:


I have disabled (unchecked) the use of the XML-RPC interface under options -> writing, as well as the Atom protocol.
Additionally I have disabled pingbacks/trackbacks from other sites under options -> discussion.

Despite this, my WP 2.6 will send the following header (shortened the irrelevant data). Notice the X-pingback:

HTTP/1.1 200 OK
Date: ...
Server: ...
X-Pingback: http://www.mysite.example/xmlrpc.php
Content-Type: ...

After grep-ing my wordpress folder I found that this header is sent in the function WP->send_headers() in classes.php line 190.

Shouldn't that function check whether that header has to be sent?
(which shouldn't be the case when disabling the XML-RPC interface or trackbacks/pingbacks, right?)

Change History (3)

#1 @Otto42
7 years ago

  • Type changed from defect to enhancement

Disabling XML-RPC does not disable the pingback functionality, nor should it, IMO.

And pingbacks and trackbacks can be enabled or disabled on a per-post basis, so if you wanted to determine when to send the header, you'd have to jump start the Loop early then rewind. Probably not worth the trouble.

Given that it really doesn't make any difference (if the pingbacks are disabled on a post, then the pingback itself is rejected), I'd mark this as not particularly important.

Also, it's an enhancement request, not a defect.

#2 @westi
7 years ago

  • Milestone changed from 2.7 to 2.9

Ott42 explains it well here. The XML-RPC publish interface is what that option disables not pingbacks/trackbacks there are per-post options.

#3 @josephscott
7 years ago

  • Milestone 2.9 deleted
  • Resolution set to invalid
  • Status changed from new to closed

And note that the pingback setting you changed was "Default article settings", not turning off pingbacks for the whole site.

I'm going to go ahead and close this as invalid.

Note: See TracTickets for help on using tickets.