Re: Escaping semicolons (actually Ampersands)
Phil Endecott wrote: > Tony> The stuff between the quotes following HREF is not HTML; it > Tony> is a URL. Hence, it must follow URL rules not HTML rules. > > No, it's both a URL and HTML. It must follow both rules. > > Please see the page that I cited in my previous message: > http://www.htmlhelp.com/tools/validator/problems.html#amp I've looked at hundreds of web pages and I've never seen anyone put & into HREF in place of an ampersand. Tony
Re: Escaping semicolons (actually Ampersands)
Tony> The stuff between the quotes following HREF is not HTML; it Tony> is a URL. Hence, it must follow URL rules not HTML rules. No, it's both a URL and HTML. It must follow both rules. Please see the page that I cited in my previous message: http://www.htmlhelp.com/tools/validator/problems.html#amp --Phil.
Re: Escaping semicolons (actually Ampersands)
Phil Endecott wrote: > Just because something works it doesn't mean it's right! My point was that it would never work. > Tony> By the way, the correct URI encoding of ampersand is "%26", > Tony> not "&". The latter encoding is used for ampersands in > Tony> HTML markup. > > But in this case I am talking HTML, hence the tags in those examples. Sorry, but you're talking about URLs. The stuff between the quotes following HREF is not HTML; it is a URL. Hence, it must follow URL rules not HTML rules. Tony
http-user and http-passwd support for https?
Hi, I have been trying to use wget to download a file from a https site that requires a user name and password. The additional complexity is that our company also uses a proxy server, for which a user name and password are required. The command I am giving is as follows: wget https://website/file.zip --proxy-user= --proxy-passwd= --proxy=on -- http-user= --http-passwd= I was using wget1.9.1, but, as mentioned in one of the mailing lists, this version did not have proper support for a https proxy. I then downloaded the latest CVS version: 1.9+cvs-dev-200404081407 and created an environment variable called https_proxy where I specified the name of our proxy server (along with the port). Now wget is able to connect to our proxy server, and send out a request, to the website using https, but it always gets a 404 Not Found error. However, we are able to download the same file if we try accessing the web page through a browser window such as IE. My doubt is, will the options http-user and http-passwd apply for https as well? Does wget have support for a https-user and https-passwd, while using https through a proxy server that also requires a user name and password? I hope my question wasn’t too confusing! We’d really appreciate a quick reply – thanks in advance! Regards, Josephine.
