Forum Moderators: open

Message Too Old, No Replies

Link Not Validating

.asp link is not valid

         

CSS_Kidd

12:42 pm on Jun 19, 2009 (gmt 0)

10+ Year Member



Here is another Validation problem. I have a few .asp links listed on a page that will not validate in XHTML 1.0 Strict.

Examples:
".asp?BzID=1358&Nav=0&S=239&L=1"
".asp?BzID=1358&to=cp&Nav=0&S=239&L=1&ID=4604"

As you can see I have already replaced the "&"s with "&"s, which normally gives me validation errors. But this time I am getting some errors for parts of the link that I am not to sure about.

Here are an errors that the W3C validator gives me.

cannot generate system identifier for general entity "Nav"
.asp?BzID=1358&"Nav"=0&S=239&L=1">

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon ";". The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Note: Although it makes a reference to the ampersand problem, I have already corrected this prior to this error by using &

Does anyone have a suggestion?

BTW: This link is being put in via html code in an html input box in a CMS. Not sure if that would have an effect?

swa66

5:27 pm on Jun 19, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



If you look at the source code in a browser (not your scritps on the server),
do you see
.asp?BzID=1358&Nav=0&S=239&L=1">

or
.asp?BzID=1358&"Nav"=0&S=239&L=1">

As far as I can tell the validator is getting the second result, which is invalid. How to make your scripts do the right thing is beyond me (I'm happy to know absolutely nothing about asp).

CSS_Kidd

7:54 pm on Jun 19, 2009 (gmt 0)

10+ Year Member



I have come to realize that it is the CMS that translates it from "&" to "&" upon publishing the content. I have created a file with those links and the same DOCTYPE and that file validated just fine. Unfortunately I have no control over how our CMS proses code upon publishing. So it is just going to have to be un-validated just because of those links.