Well, after looking for, copying/pasting, testing, changing and
looking for again, it seems that my problem was that i needed to add
the following line into my virtual host:443
SSLProxyEngine on
Now it's working
Thanks all for your responses, your help and your patient
Regards,
Andres
2012/2/2
Yes, into httpd-ssl.conf
# Note: Configurations that use IPv6 but not IPv4-mapped addresses need two
# Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443"
#
Listen 8443
2012/2/20 Igor Cicimov :
> Do you have
> Listen 8443
> at all in your config?
>
> On Feb 20, 2012 10:28 PM, "A
Do you have
Listen 8443
at all in your config?
On Feb 20, 2012 10:28 PM, "Andres Aguado" wrote:
> m, i've configured on other machine, other apache 2.2 as reverse
> proxy and i've forwarded request to https://www.ingdirect.es, and the
> error is the same
>
> This is a very strange cuestion b
m, i've configured on other machine, other apache 2.2 as reverse
proxy and i've forwarded request to https://www.ingdirect.es, and the
error is the same
This is a very strange cuestion but, do you know if these
configurations should work?, is it necessary to make any strange
configuration?
Re
Hi again. Here we are again
Sorry, but I don't understand that dns error, because i'm connecting
to ip interface. I'm not connecting to dns name to simplify the issue.
And i can connect from proxy to backend ok to https port. the problem
seems to be when virtual host "proxypass" the request, becau
On Fri, Feb 17, 2012 at 10:28 AM, Igor Cicimov wrote:
> You have DNS error. Also check if you can connect from the proxy to the
> backend on ssl port.
proxy: DNS
lookup failure for: 192.168.112.57spipe returned by /spipe/pkg
That looks more like a configuration problem... The path is
unexpected
You have DNS error. Also check if you can connect from the proxy to the
backend on ssl port.
On Feb 18, 2012 1:04 AM, "Andres Aguado" wrote:
> Hi again Igor, connecting to https://192.168.112.57 directly, a
> websphere app server (the backend app server for my case) admin page
> is shown
>
> The
Hi again Igor, connecting to https://192.168.112.57 directly, a
websphere app server (the backend app server for my case) admin page
is shown
The error log shows this files since startup
The Apache2.2 service has restarted.
arent: Received restart signal -- Restarting the server.
[Fri Feb 17 14:1
What is in the error file dude not the access one? Since you are proxying
to https://192.168.112.57 do you have ssl enabled on that server? What do
you see in its log file?
Since you said http proxying works i suspect you don't have ssl configured
on the backend 192.168.112.57.
On Fri, Feb 17, 20
Sorry Tom, here is an important piece of httpd-ssl.conf
SSLEngine on #Behind proxypass sentences
SSLCertificateFile "C:\Program Files (x86)\Apache Software
Foundation\Apache2.2\conf\ssl\server.crt"
SSLCertificateKeyFile "C:\Program Files (x86)\Apache Software
Foundation\Apache2.2\conf\ssl\server
On Thu, Feb 16, 2012 at 2:31 PM, Andres Aguado wrote:
> Hi all, i'd like to expose my problem because i'm going crazy, and if
> anyone could help me it'll be very appreciated.
>
> Well, I've an apache 2.2 server over win2k8, and i want to configure
> it as reverse proxy to send request to backend
Sorry Hridayesh, yesterday i was a bit locked and i forgot to explain
the internal server error
2012/2/17 Andres Aguado :
> Hi Igor, it seems that reverse proxy is malfunctioning for https. If i
> proxypass to http link of destination app server it works fine, but
> when i try to proxypass to http
Hi Igor, it seems that reverse proxy is malfunctioning for https. If i
proxypass to http link of destination app server it works fine, but
when i try to proxypass to https link, my web explorer shows "500
internal server error - The server encountered an internal error or
misconfiguration and was u
In firefox it will show that This Connection is Untrusted, but in the last
there is option "I understand the risk" Clicking on that will show a button
to add exception. After adding exception you can continue.
Remember it will work on your system only after adding exception. Every one
who wants to
What doesnt work? What link are you trying to access? What errors are in
the log files?
On Feb 17, 2012 8:30 PM, "Andres Aguado" wrote:
> Hi Hridayesh, and thanks for your response, but it doesn't work in
> firefox. The same error is displayed.
>
> Other idea?
> Thanks for your help
> Regads
> A
Hi Hridayesh, and thanks for your response, but it doesn't work in
firefox. The same error is displayed.
Other idea?
Thanks for your help
Regads
Andres
2012/2/17 Hridayesh Gupta :
> It looks like you are trying to setup reverse proxy in https(port 443).
> Which is working but browser is not able
It looks like you are trying to setup reverse proxy in https(port 443).
Which is working but browser is not able to verify certificate. I believe
if you try this setup under http (port 80) it will work.
Certificate might be signed by https://192.168.112.57 correctly but it in
that case it would be
Hi all, i'd like to expose my problem because i'm going crazy, and if
anyone could help me it'll be very appreciated.
Well, I've an apache 2.2 server over win2k8, and i want to configure
it as reverse proxy to send request to backend Websphere server
So, my httpd.conf file is written like this:
18 matches
Mail list logo
