Re: HTML entities in URLs and urlencoding

The escaped ampersand doesn't break any of the URLs that I use regularly...in fact when I write straight xhtml I encode them in my URLs so that my pages still pass the xhtml 1.0 strict. On Mar 31, 2008, at 9:45 PM, Waylan Limberg wrote: Is there something I'm missing or is this a bug? As far

On ampersands in query strings (was: HTML entities in URLs and urlencoding)

* Waylan Limberg <[EMAIL PROTECTED]> [2008-04-01 03:50]: > As far as I can tell, the "&" breaks the query string. No, it doesn’t, as you found out. However, on a tangential note: if you write web apps, *please* make sure that you support the semicolon as a query parameter separator as well as the

Re: HTML entities in URLs and urlencoding

On Mon, Mar 31, 2008 at 9:53 PM, Milian Wolff <[EMAIL PROTECTED]> wrote: [snip] > > > > So the "&" must not be escaped! > > It must! See also > Doh'! I knew that. Of course, I just typed a url with an & in my address bar and it didn't work.

Re: HTML entities in URLs and urlencoding

Am Dienstag, 1. April 2008 schrieb Waylan Limberg: > We recently received the following bug report for the python-markdown > > implementation: > > The "&" are escaped in URLs. > > > > An example: > > [Link](http://www.site.com/?param1=value1¶m2=value1) > > > > Should output: > > http://www.

HTML entities in URLs and urlencoding

We recently received the following bug report for the python-markdown implementation: > The "&" are escaped in URLs. > > An example: > [Link](http://www.site.com/?param1=value1¶m2=value1) > > Should output: > http://www.site.com/?param1=value1¶m2=value1";>Link > > Currently outputs: >