Yes Stephen that is true. Any URL being sent from HTML should be encoded
as good programming practice. IN your case the particular link itself is
incorrect.
-----Original Message-----
From: Stephen.Harrington [mailto:Ste...@tr...]
Sent: Monday, September 30, 2002 9:52 PM
To: htmlparser-user
Subject: [Htmlparser-user] Not my link....
Dhaval posted:
Hi Stephen,
Using '>' in your link is incorrect since it is a special character in
HTML. What I am saying is that your code is incorrect. Your query string
must be scaped before sending tot he server. You must use the hex
representation of > in your link
i.e. %3E.
This should not only make your HTML correct but will solve your parsing
problem as well.
Regards,
Dhaval Udani
Senior Analyst
M-Line, QPEG
OrbiTech Solutions Ltd.
+91-22-8290019 Extn. 1457
------------------------------------------------------------------------
---------------------
Unfortunately I am not the author of the page I a parsing. BTW, this
was NOT a problem in the last production build. It only arose for me
when I went to the latest integration build.
So if I understand your comment, if the link were URL encoded before
getting sent to the parser this would not be a problem?
--stephen
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Htmlparser-user mailing list
Htm...@li...
https://lists.sourceforge.net/lists/listinfo/htmlparser-user
|