|
Posted by Harlan Messinger on December 17, 2007, 1:12 pm
Please log in for more thread options mark4asp wrote:
> Harlan Messinger wrote:
>
>> mark4asp wrote:
>>> When I write a url in xhtml, with an unencoded ampersand, like this:
>>>
>>> http://localhost:2063/Client/ViewReport.aspx?Ref=58&Type=SUMMARY
>>>
>>> the xhtml sytax checker correctly indicates an error, telling me
>>> that it should be:
>>>
>>> http://localhost:2063/Client/ViewReport.aspx?Ref=58&Type=SUMMARY
>>>
>>> see: <http://www.htmlhelp.com/tools/validator/problems.html#amp>
>>>
>>> However the last sentence there ends:
>>>
>>> "the browser translates "&" to "&" so the Web server would only
>>> see "&" and not "&" in the query string of the request."
>>>
>>> My web server is clearly seeing & and the browser (FF 1.0.0.11)
>>> is also showing & in the url.
>>>
>>> I am using:
>>> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
>>> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
>>>
>>> with no xml prefix because, as we all know, IE6 breaks when the xml
>>> prefix is present.
>>>
>>> What is the cause and solution of this problem.
>>>
>>> I am using FF 1.0.0.11, via a local asp.net 2.0 site through the
>>> mini webserver (Cassini) on WinXP SP2 with all latest o/s updates
>>> installed (apart from IE7, I am using IE6 on this PC).
>> You're using 1.0.0.11? The bug is that it's practically the very
>> first version released and it was superseded by 1.0.1 within a couple
>> of months, by 1.5 over two years ago, and by 2.0 over a year ago.
>> Based on usage of the high-traffic site I'm involved with, virtually
>> no one is using Firefox 1.x any more (probably because Firefox
>> prompts you to update it), and you certainly shouldn't be doing
>> anything with a version that has been outdated over ten times as long
>> as the product had existed when the version was replaced.
>
> Apologies, a typo. I am using FF 2.0.0.11
>
>>> Do I have to apply a url decode algorithm when the web page loads?
>>> That is far from ideal because the problem here is that the browser
>>> is not showing the decoded url.
>>>
>>> Is this a bug in FF?
>> There is no problem with this whatsoever in Firefox 2, I can tell you
>> that. Use & in your links and images and so forth and it'll work.
>
> So exactly what should happen.
>
> If I have, say:
> <a href="../page1.aspx?a=1&b=gonow">Go Now</a>
> in my html, on clicking the link, will FF give :
> blah blah/page1.aspx?a=1&b=gonow
> in the address bar?
>
> It's not doing that for me. It gives
> blah blah/page1.aspx?a=1&b=gonow
I don't see how that's happening. I just built a page called
amp_in_url.html as follows:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Amp in URL</title>
</head>
<body>
<h1>Amp in URL</h1>
<p><a href="amp_in_url.html?a=1&b=gonow">Go Now</a></p>
</body>
</html>
When I hover the cursor over the link Firefox's status bar reads
http://www.[mycompany].com/amp_in_url.html?a=1&b=gonow
When I click the link, IIS's log entry includes:
80 GET /amp_in_url.html a=1&b=gonow 200
(port 80, method GET, path /amp_in_url.html, querystring a=1&b=gonow,
status 200).
The result is the same if I switch to XHTML.
>
> Which the server reads and tells me that it can't get my querystrings.
> I suppose I can url decode this at the server end to fix it.
>
>
| 
XML Sitemap