Opened 9 years ago
Closed 8 years ago
#37300 closed enhancement (fixed)
Add 'urn' to allowed protocols
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 4.7 | Priority: | normal |
Severity: | normal | Version: | |
Component: | General | Keywords: | has-patch |
Focuses: | Cc: |
Description
'urn' should be the safest protocol to allow on the planet as it doesn’t do much, except act as an identifier in various XML schemes.
the_guid()
currently uses esc_url()
as a default filter, meaning urn:uuid:<hash>
can’t be used as a guid in feeds ithout first allowing the urn protocol. The Atom feed standard shows most examples with a urn:uuid used as the ID. (IDs in Atom must be URIs so using esc_url() still makes perfect sense.)
The attach patch adds the urn protocol to the list of allowed protocols. (See RFC 2141 for details on the protocol schema.)
Work-around: print( get_the_guid() );
doesn’t apply any default filters like the_guid() does.
Attachments (4)
Change History (10)
#1
@
9 years ago
- Keywords has-patch added
- Milestone changed from Awaiting Review to Future Release
- Type changed from defect (bug) to enhancement
- Version trunk deleted
Note: See
TracTickets for help on using
tickets.
@geekysoft Thanks for the ticket and the patch, looks good to me. The function needs only a new changelog entry for the new protocol, see [32346] for 'webcal'.