[users@httpd] Apache2.2 issue

[shalini jonnadula <va...@gmail.com>]

Hi,

Recently i have upgraded Apache 1.3 to Apache 2.2 on my Solaris box.
version 2.2 is working fine but i have problem of "Proxy Error and it is
giving the reason as Reason: DNS lookup failure for: xyz.com"

Here is my problem senario. Apache is running on server with Apache 1.3
>From solaris client i was able to connect to server with www.xyz.com,
here client side i didn't setup either NIS/DNS setup to resolve
xyz.com, but only server entry in /etc/hosts file.
with/without ssl it is working fine.

But when i upgraded to apache2.2
there is no change in client. http://www.xyz.com in working fine but
https://www.xyz.com (SSL) is not resolving the server IP.

you replied me that it is not a DNS problem and suggested to  Check the
output of running `apache2ctl -S` on my server. this command gave output as

VirtualHost configuration:
Syntax OK

it doesn't list anything.

can u plz help me resolve this issue by anyother way?


Thanks.

Re: [users@httpd] Apache2.2 issue

[shalini jonnadula <va...@gmail.com>]

Recently i have upgraded Apache 1.3 to Apache 2.2 on my Solaris box.
version 2.2 is working fine for http but i have problem of "The requested
method CONNECT is not allowed for the URL /index.html." for https.
i'm sending my httpd.conf file also can u please see this issue?
Thanks in advance....

RE: [users@httpd] Apache2.2 issue

[Ashwin Kesavan <as...@yahoo-inc.com>]

Hi,

My replies in line below

From: shalini jonnadula [mailto:vasantha.shalini@gmail.com]
Sent: Thursday, May 26, 2011 7:10 PM
To: users@httpd.apache.org
Subject: [users@httpd] Apache2.2 issue

Hi,

Recently i have upgraded Apache 1.3 to Apache 2.2 on my Solaris box.
version 2.2 is working fine but i have problem of "Proxy Error and it is giving the reason as Reason: DNS lookup failure for: xyz.com<http://xyz.com>"

Here is my problem senario. Apache is running on server with Apache 1.3
>From solaris client i was able to connect to server with www.xyz.com<http://www.xyz.com>,
here client side i didn't setup either NIS/DNS setup to resolve
xyz.com<http://xyz.com>, but only server entry in /etc/hosts file.
with/without ssl it is working fine.

But when i upgraded to apache2.2
there is no change in client. http://www.xyz.com in working fine but
https://www.xyz.com (SSL) is not resolving the server IP.

Ashwin says

Is the hit recorded in httpd access log? Do tail -f /path/to/accessLog and see if hits are coming to the httpd server and what is the server response. Try running wireshark to see what is happening on the network when SSL handshake happens. These are basic troubleshooting steps, so might sound silly, but some seemingly difficult problem are often such silly problem over seen .Is it listening on the right port and right ip address?

HTH

--ashwin