dillo won't resolve URLs under a proxy environment?
Hi; Dillo looks interesting. However I can't go anywhere with it as I am under a proxy environment. I saw that the default dillorc has a commented-out section for http_proxy. I copied the default dillorc to be my ~/.dillorc and started dillo again. I noticed that the chatter from dillo no longer complained about a missing .dillorc, yet I am still unable to go to any URL. The message on the web browser was: "Error: Dns: can't resolve http://linuxtoday.com". I get the same basic error message when trying to go to www.perl.com or http://www.perl.com. I am able to go to these web sites using other web browsers such as mozilla, galeon, opera, netscape and konqueror. Each one of those I had to set a proxy preference. Perhaps my proxy setting has incorrect syntax? Enclosed is the chatter from dillo and the .dillorc (proxy setting has obviously been sanitized). Thanks, Ken **************snip********************** prompt> cat /etc/redhat-release Red Hat Linux release 8.0 (Psyche) prompt> which dillo dillo is /usr/bin/dillo ptompt> dillo --version Dillo 0.7.3 /msa3530> prompt> dillo Setting locale to C... dillo_dns_init: Here we go! Disabling cookies. Nav_open_url: Url=>about:splash< Nav_open_url: Url=>http://linuxtoday.com/<; Dns_server [0]: linuxtoday.com is (nil) Dillo: normal exit! /prompt> **************snip********************** **************snip********************** http_proxy=http://my_ip:my_port/ **************snip**********************
On Wed, 12 Nov 2003 10:53:45 -0600 Ken Wolcott <ken.wolcott@med.ge.com> wrote:
Hi;
Dillo looks interesting. However I can't go anywhere with it as I am under a proxy environment. I saw that the default dillorc has a commented-out section for http_proxy. I copied the default dillorc to be my ~/.dillorc and started dillo again.
you DID uncomment the http_proxy line and edit it to insert YOUR proxy's address? (using a local wwwoffle proxy on my notebook) $ grep -i proxy .dillo/dillorc # Set the proxy information for http http_proxy=http://localhost:8080/ no_proxy = "wl localhost" note that plain dillo does currently NOT support proxy authentication.
I noticed that the chatter from dillo no longer complained about a missing .dillorc, yet I am still unable to go to any URL. The message on the web browser was: "Error: Dns: can't resolve http://linuxtoday.com". I get the same basic error message when trying to go to www.perl.com or http://www.perl.com. I am able to go to these web sites using other web browsers such as mozilla, galeon, opera, netscape and konqueror. Each one of those I had to set a proxy preference. Perhaps my proxy setting has incorrect syntax? Enclosed is the chatter from dillo and the .dillorc (proxy setting has obviously been sanitized).
Thanks, Ken
prompt> dillo Nav_open_url: Url=>http://linuxtoday.com/<; Dns_server [0]: linuxtoday.com is (nil)
when using a proxy, dillo would never try to resolve the DNS of the URL you entered, but only connect to the proxy host: $ dillo Enabling cookies as from cookiesrc... Connecting to 127.0.0.1 Greetings, Thorben
Hi Thorben; Thank you for your response. Yes, I didn't make myself very clear unfortunately, and I realized that some time after having sent the email msg. I did a diff of the supplied dillorc and my ~/.dillorc. The only line that differed was the extra line (copied http_proxy) that I had enabled with the correct URL for the proxy. What I provided in the email was the line that diff'd after it had been "sanitized". I had an "Automatic proxy configuration URL" set up for mozilla originally which is different than a "Manual proxy configuration" (http://ip:port) syntax. I decided to change the way the proxy was configured in mozilla to the form needed by dillo. It works fine. Are you saying that dillo under a proxy expects the proxy server to do all dns resolution? If that's the case, then why is galeon, mozilla, konquorer, netscape and opera working correctly under the proxy where dillo does not? I'm using the same proxy for all the web browsers I just mentioned. Thanks, Ken On Wednesday 12 November 2003 13:08, Thorben Thuermer wrote:
On Wed, 12 Nov 2003 10:53:45 -0600
Ken Wolcott <ken.wolcott@med.ge.com> wrote:
Hi;
Dillo looks interesting. However I can't go anywhere with it as I am under a proxy environment. I saw that the default dillorc has a commented-out section for http_proxy. I copied the default dillorc to be my ~/.dillorc and started dillo again.
you DID uncomment the http_proxy line and edit it to insert YOUR proxy's address?
(using a local wwwoffle proxy on my notebook) $ grep -i proxy .dillo/dillorc # Set the proxy information for http http_proxy=http://localhost:8080/ no_proxy = "wl localhost"
note that plain dillo does currently NOT support proxy authentication.
I noticed that the chatter from dillo no longer complained about a missing .dillorc, yet I am still unable to go to any URL. The message on the web browser was: "Error: Dns: can't resolve http://linuxtoday.com". I get the same basic error message when trying to go to www.perl.com or http://www.perl.com. I am able to go to these web sites using other web browsers such as mozilla, galeon, opera, netscape and konqueror. Each one of those I had to set a proxy preference. Perhaps my proxy setting has incorrect syntax? Enclosed is the chatter from dillo and the .dillorc (proxy setting has obviously been sanitized).
Thanks, Ken
prompt> dillo Nav_open_url: Url=>http://linuxtoday.com/<; Dns_server [0]: linuxtoday.com is (nil)
when using a proxy, dillo would never try to resolve the DNS of the URL you entered, but only connect to the proxy host:
$ dillo Enabling cookies as from cookiesrc... Connecting to 127.0.0.1
Greetings, Thorben
_______________________________________________ Dillo-dev mailing list Dillo-dev@lists.auriga.wearlab.de http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev
On Wed, 12 Nov 2003 13:43:34 -0600 Ken Wolcott <ken.wolcott@med.ge.com> wrote:
Hi Thorben;
Thank you for your response.
Yes, I didn't make myself very clear unfortunately, and I realized that some time after having sent the email msg.
I did a diff of the supplied dillorc and my ~/.dillorc. The only line that differed was the extra line (copied http_proxy) that I had enabled with the correct URL for the proxy. What I provided in the email was the line that diff'd after it had been "sanitized".
I had an "Automatic proxy configuration URL" set up for mozilla originally which is different than a "Manual proxy configuration" (http://ip:port) syntax. I decided to change the way the proxy was configured in mozilla to the form needed by dillo. It works fine.
Dillo does not support those either, it needs the actual address and port of the proxy. as long as your dillo tries to dns resolve the host of the url you enter, it is for some reason NOT using a proxy at all.
Are you saying that dillo under a proxy expects the proxy server to do all dns resolution? If that's the case, then why is galeon, mozilla, konquorer, netscape and opera working correctly under the proxy where dillo does not? I'm using the same proxy for all the web browsers I just mentioned.
sorry, but: THIS IS HOW PROXY SERVERS WORK! the browsr forwards the proxy the request "get me http://www.dillo.org/" (to be exact: GET http://www.dillo.org/ HTTP/1.0") and the proxy returns the page/image/resource, or a error.
Thanks, Ken
greetings, Thorben
On Wednesday 12 November 2003 13:53, Thorben Thuermer wrote:
On Wed, 12 Nov 2003 13:43:34 -0600
Ken Wolcott <ken.wolcott@med.ge.com> wrote:
Hi Thorben;
Thank you for your response.
Yes, I didn't make myself very clear unfortunately, and I realized that some time after having sent the email msg.
I did a diff of the supplied dillorc and my ~/.dillorc. The only line that differed was the extra line (copied http_proxy) that I had enabled with the correct URL for the proxy. What I provided in the email was the line that diff'd after it had been "sanitized".
I had an "Automatic proxy configuration URL" set up for mozilla originally which is different than a "Manual proxy configuration" (http://ip:port) syntax. I decided to change the way the proxy was configured in mozilla to the form needed by dillo. It works fine.
Dillo does not support those either, it needs the actual address and port of the proxy. as long as your dillo tries to dns resolve the host of the url you enter, it is for some reason NOT using a proxy at all.
Are you saying that dillo under a proxy expects the proxy server to do all dns resolution? If that's the case, then why is galeon, mozilla, konquorer, netscape and opera working correctly under the proxy where dillo does not? I'm using the same proxy for all the web browsers I just mentioned.
sorry, but: THIS IS HOW PROXY SERVERS WORK!
the browsr forwards the proxy the request "get me http://www.dillo.org/" (to be exact: GET http://www.dillo.org/ HTTP/1.0") and the proxy returns the page/image/resource, or a error.
Thanks, Ken
greetings, Thorben
Hi Thorben; If my proxy server refuses to resolve requests coming from the dillo web browser, it doesn't make any sense for it not to refuse requests from the mozilla web browser. The proxy settings are identical. One of them exists in the ~/.dillorc and the other exists in the mozilla advanced proxy setting preferences. So, it looks to me like dillo doesn't like my ~/.dillorc and isn't telling me that there's a problem. Mozilla works fine, dillo doesn't, the proxy settings are the same. Ken
At 12:18 PM 11/12/2003, Ken Wolcott wrote:
If my proxy server refuses to resolve requests coming from the dillo web browser, it doesn't make any sense for it not to refuse requests from the mozilla web browser. The proxy settings are identical. One of them exists in the ~/.dillorc and the other exists in the mozilla advanced proxy setting preferences. So, it looks to me like dillo doesn't like my ~/.dillorc and isn't telling me that there's a problem. Mozilla works fine, dillo doesn't, the proxy settings are the same.
The impression I get from the earlier posts is not that your proxy server is not resolving requests from Dillo, but that Dillo is not sending requests to the proxy server. As Thorben stated:
Dillo does not support those either, it needs the actual address and port of the proxy.
So if you use the IP address or a name listed in /etc/hosts, it sounds like it should work. (I've never used a proxy with Dillo, I'm just basing this on what I've read today.) Kelson Vibber www.hyperborea.org
On Wed, 12 Nov 2003 14:18:38 -0600 Ken Wolcott <ken.wolcott@med.ge.com> wrote:
[...] The proxy settings are identical. One of them exists in the ~/.dillorc and the other exists in the mozilla advanced proxy setting preferences. So, it looks to me like dillo doesn't like my ~/.dillorc and isn't telling me that there's a problem. Mozilla works fine, dillo doesn't, the proxy settings are the same.
Well, the dillorc provided in the Dillo-tarball should recide in ~/.dillo/ - i.e. the path should be ~/.dillo/dillorc and NOT ~/.dillorc - Victor
On Wed, 12 Nov 2003 14:18:38 -0600 Ken Wolcott <ken.wolcott@med.ge.com> wrote:
Hi Thorben;
If my proxy server refuses to resolve requests coming from the dillo web browser, it doesn't make any sense for it not to refuse requests from the mozilla web browser. The proxy settings are identical. One of them exists in the ~/.dillorc and the other exists in the mozilla advanced proxy setting preferences. So, it looks to me like dillo doesn't like my ~/.dillorc and isn't telling me that there's a problem. Mozilla works fine, dillo doesn't, the proxy settings are the same.
it's not a problem of your proxy not liking dillo's requests: ****
as long as your dillo tries to dns resolve the host of the url you enter, it is for some reason NOT using a proxy at all.
- your dillo does not use any proxy setting. - i do not know why. it's probably something simple... maybe try something like: $ mv .dillo/dillorc .dillo/dillorc.bak $ echo http_proxy=http://localhost:12345/ >.dillo/dillorc ^^^^^^^^^^^^^^ $ dillo http://www.google.com/ Enabling cookies as from cookiesrc... Connecting to 127.0.0.1 ... just read Victor's reply while writing this... but then what was
I noticed that the chatter from dillo no longer complained about a missing .dillorc about?
Ken
Thorben
On Wed, Nov 12, 2003 at 09:57:39PM +0100, Thorben Thuermer wrote:
... just read Victor's reply while writing this...
but then what was
I noticed that the chatter from dillo no longer complained about a missing .dillorc about?
I think you'll find that was a misinterpretation of Dillo: error reading /home/<user>/.dillo: No such file or directory Which gets created, so the next time you run dillo it doesn't complain. -- Stephen Lewis
On Wednesday 12 November 2003 15:08, Stephen Lewis wrote:
On Wed, Nov 12, 2003 at 09:57:39PM +0100, Thorben Thuermer wrote:
... just read Victor's reply while writing this...
but then what was
I noticed that the chatter from dillo no longer complained about a missing .dillorc
about?
I think you'll find that was a misinterpretation of
Dillo: error reading /home/<user>/.dillo: No such file or directory
Which gets created, so the next time you run dillo it doesn't complain.
Exactly what happened to me, now that I think about it. Thanks, Ken
On Wednesday 12 November 2003 14:57, Thorben Thuermer wrote:
On Wed, 12 Nov 2003 14:18:38 -0600
Ken Wolcott <ken.wolcott@med.ge.com> wrote:
Hi Thorben;
If my proxy server refuses to resolve requests coming from the dillo web browser, it doesn't make any sense for it not to refuse requests from the mozilla web browser. The proxy settings are identical. One of them exists in the ~/.dillorc and the other exists in the mozilla advanced proxy setting preferences. So, it looks to me like dillo doesn't like my ~/.dillorc and isn't telling me that there's a problem. Mozilla works fine, dillo doesn't, the proxy settings are the same.
it's not a problem of your proxy not liking dillo's requests:
****
as long as your dillo tries to dns resolve the host of the url you enter, it is for some reason NOT using a proxy at all.
****
- your dillo does not use any proxy setting.
- i do not know why.
it's probably something simple...
maybe try something like: $ mv .dillo/dillorc .dillo/dillorc.bak $ echo http_proxy=http://localhost:12345/ >.dillo/dillorc ^^^^^^^^^^^^^^ $ dillo http://www.google.com/ Enabling cookies as from cookiesrc... Connecting to 127.0.0.1
... just read Victor's reply while writing this...
but then what was
I noticed that the chatter from dillo no longer complained about a missing .dillorc
about?
Ken
Thorben
_______________________________________________ Dillo-dev mailing list Dillo-dev@lists.auriga.wearlab.de http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev
Hi Thorben; Problem solved. The problem was that I incorrectly thought that the rc file should be ~/.dillorc instead of ~/.dillo/dillrc. Thanks, Ken
participants (5)
-
Kelson Vibber -
Ken Wolcott -
Stephen Lewis -
Thorben Thuermer -
Victor Sahlstedt