Bug 14754 – URL Encoding stripped for space characters

• Status: RESOLVED
• Resolution: INVALID
• Component: WebCore Misc.

[Gibbons Burke]

If I use the "Mail Link to This Page..." command on the URL above it unencodes the URL so that the occurrences of "%20" are transformed into actual space characters. This works ok in the original html email format because it also turns it into a link, but if I send this to a mailing list which turns it into plain text, the spaces break the URL up and it no longer works well as a link in many email clients.

I have a javascript bookmark in my Safari bookmark bar which does what the "Mail Link to this Page..." command does, but is different: It encloses the URL within angle braces as a way of telling some email clients that the URL, if it spans lines should be considered one line of text. Here's the javascript:

javascript:location.href='mailto:?SUBJECT='+document.title+%20'&BODY='+document.title+'%5Cn%3C'+escape(location.href)+'%3E'

This script has the same problem - the URL-coded space characters are turned into spaces and the URL doesn't work when the mail, if it is sent in plain text, at the receiver's end.

[David Kilzer (:ddkilzer)]

How to other browser behave, e.g., MSIE 6/7, Firefox 2.0.0.x, or Opera 9.21?

[Alexey Proskuryakov]

See also: bug 14555, bug 11740, bug 13146.

[Alexey Proskuryakov]

This is not a WebKit or even a Safari issue, as we send an unencoded URL to the mail client. This should be reported against Mail.app in Radar.

Below is a dump of an Apple event received by Mail.app from Safari.

AE2000 (57492): Received an event:
------oo start of event oo------
{ 1 } 'aevt':  mail/mllk (i386){
          return id: 0 (0x0)
     transaction id: 0 (0x0)
  interaction level: 112 (0x70)
     reply required: 1 (0x1)
             remote: 0 (0x0)
      for recording: 0 (0x0)
         reply port: 36635 (0x8f1b)
  target:
    { 1 } 'psn ':  8 bytes {
      { 0x0, 0x3c03c0 } (Safari)
    }
  fEventSourcePSN: { 0x0,0x3c03c0 } (Safari)
  optional attributes:
    < empty record >
  event data:
    { 1 } 'aevt':  - 2 items {
      key '----' - 
        { 1 } 'utxt':  604 bytes {
          "http://a1135.g.akamai.net/f/1135/18227/1h/cchannel.download.akamai.com/18227/podcast/NEWORLEANS-LA/WRNO-FM/Rob%20&%20Henry.mp3?CPROG=PCAST&MARKET=NEWORLEANS-LA&NG_FORMAT=newstalk&SITE_ID=3632&STATION_ID=WRNO-FM&PCAST_AUTHOR=thenew995fm.com&PCAST_CAT=News_%26_Talk&PCAST_TITLE=Rob_%26_Bo_Audio_On_Demand"
        }
      key 'urln' - 
        { 1 } 'utxt':  604 bytes {
          "http://a1135.g.akamai.net/f/1135/18227/1h/cchannel.download.akamai.com/18227/podcast/NEWORLEANS-LA/WRNO-FM/Rob%20&%20Henry.mp3?CPROG=PCAST&MARKET=NEWORLEANS-LA&NG_FORMAT=newstalk&SITE_ID=3632&STATION_ID=WRNO-FM&PCAST_AUTHOR=thenew995fm.com&PCAST_CAT=News_%26_Talk&PCAST_TITLE=Rob_%26_Bo_Audio_On_Demand"
        }
    }
}

[Robert Blaut]

(In reply to comment #3)
> This is not a WebKit or even a Safari issue, as we send an unencoded URL to the
> mail client. This should be reported against Mail.app in Radar.

So we should close the report.

[Alexey Proskuryakov]

<rdar://problem/6106984>