Talk:URL encoding: Difference between revisions
Content added Content deleted
m (format fix) |
No edit summary |
||
| Line 11: | Line 11: | ||
::: Would only be encoded if this URL were being passed as data within another URL. See the RFC sections on Reserved Characters and When to Encode or Decode. |
::: Would only be encoded if this URL were being passed as data within another URL. See the RFC sections on Reserved Characters and When to Encode or Decode. |
||
:::: The task is to demonstrate the encoding mechanism, rather than when to use the application of this, so we can assume that this will be used in applications where the URL string requires encoding. --[[User:Markhobley|Markhobley]] 13:01, 17 June 2011 (UTC) |
:::: The task is to demonstrate the encoding mechanism, rather than when to use the application of this, so we can assume that this will be used in applications where the URL string requires encoding. --[[User:Markhobley|Markhobley]] 13:01, 17 June 2011 (UTC) |
||
::::: Fair enough. --[[User:Dgamey|Dgamey]] 01:43, 19 June 2011 (UTC) |
|||
:: There probably should be soome required input(s) and output(s). I noticed the perl example is very cryptic using a library and provides no output. The output it would produce doesn't match the 'example' string as it only encodes data in the path portion of the URL and not the entire URL. |
:: There probably should be soome required input(s) and output(s). I noticed the perl example is very cryptic using a library and provides no output. The output it would produce doesn't match the 'example' string as it only encodes data in the path portion of the URL and not the entire URL. |
||
: --[[User:Dgamey|Dgamey]] 09:54, 17 June 2011 (UTC) |
: --[[User:Dgamey|Dgamey]] 09:54, 17 June 2011 (UTC) |
||