Make WordPress Core

Opened 12 years ago

Last modified 5 years ago

#20214 new defect (bug)

Pingback discovery doesn't strip fragment identifiers from URL

Reported by: solarissmoke's profile solarissmoke Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.3
Component: Pings/Trackbacks Keywords: needs-refresh dev-feedback
Focuses: Cc:

Description

To reproduce:

  1. Insert a link containing a fragment identifier into a post, e.g., http://localhost/wp/helloworld/#comments.
  2. Save post.
  3. Observe the URL which WordPress attempts to retrieve in discover_pingback_server_uri() - the requested path contains the #fragment_identifier, which it shouldn't, and in most cases will result in a 404, thus the pingback fails.

Attachments (1)

20214.patch (605 bytes) - added by kurtpayne 12 years ago.

Download all attachments as: .zip

Change History (4)

#1 @SergeyBiryukov
12 years ago

  • Keywords needs-patch added

#2 @kurtpayne
12 years ago

  • Cc kpayne@… added
  • Keywords has-patch added; needs-patch removed

This happens for enclosures, too. Those URLs should not be changed, right?

@kurtpayne
12 years ago

#3 @chriscct7
9 years ago

  • Keywords needs-refresh dev-feedback added; has-patch removed
Note: See TracTickets for help on using tickets.