Opened 15 years ago
Last modified 7 years ago
#20214 new defect (bug)
Pingback discovery doesn't strip fragment identifiers from URL
| Reported by: | solarissmoke | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Pings/Trackbacks | Version: | 3.3 |
| Severity: | normal | Keywords: | needs-refresh dev-feedback |
| Cc: | Focuses: |
Description
To reproduce:
- Insert a link containing a fragment identifier into a post, e.g.,
http://localhost/wp/helloworld/#comments. - Save post.
- 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)
Change History (4)
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
This happens for enclosures, too. Those URLs should not be changed, right?