sent it directly to your email address
Filip
c. wrote:
seriously? if so can you send me the link?
if not just call me gullible.
On 3/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Mladen Turk wrote:
> Filip Hanik - Dev Lists wrote:
>> or simply set a few headers in httpd when th
seriously? if so can you send me the link?
if not just call me gullible.
On 3/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Mladen Turk wrote:
> Filip Hanik - Dev Lists wrote:
>> or simply set a few headers in httpd when the request came in over
>> SSL, and then have a filter read
Mladen Turk wrote:
Filip Hanik - Dev Lists wrote:
or simply set a few headers in httpd when the request came in over
SSL, and then have a filter read those headers
OK, by now, I think everyone are aware that you
don't like the AJP protocol.
being on the support side of it has not been fun
Filip Hanik - Dev Lists wrote:
or simply set a few headers in httpd when the request came in over SSL,
and then have a filter read those headers
OK, by now, I think everyone are aware that you
don't like the AJP protocol.
You should blog about that :)
Regards,
Mladen.
--
or simply set a few headers in httpd when the request came in over SSL,
and then have a filter read those headers
Filip
Rainer Jung wrote:
Usually there are SSL problems with (reverse) proxying concerning URLs
for redirects, since the Tomcat side doesn't "know" any longer that
SSL has been sp
As a first approximation this is true. But ProxyPassReverse does not
rewrite the body of responses. So if there is a wrong URL in the body,
then this will not be fixed by ProxyPassReverse. It is mostly (or only?)
for fixing the Location header in http redirects.
Regards,
Rainer
Erik Melkerss
Usually there are SSL problems with (reverse) proxying concerning URLs
for redirects, since the Tomcat side doesn't "know" any longer that SSL
has been spoken originally. So self-referencing URLs use http as the
protocol. AJP fixes this, which is the correct interpretation of AJP
supporting SSL
and while we're on the subject, what's the difference b/w proxyPass and
ProxyPassReverse in laymens terms?
I think thats a question for the Apache-web server mailinglist but...
ProxyPass "forwards" the request from the user to another web server
ProxyPassReverse "rewrites" the response from the
c. wrote:
so would it make sense to assume that since SSL worked without any extra
config changes when I added the AJP config that it should work without
any
changes when using mod_proxy_http?
correct, the info I gave you is for when you want SSL between apache and
tomcat, you are obviously ta
so would it make sense to assume that since SSL worked without any extra
config changes when I added the AJP config that it should work without any
changes when using mod_proxy_http?
On 3/23/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
AJP doesn't use SSL, never has, so I'm not sure w
AJP doesn't use SSL, never has, so I'm not sure what the problem would be
the only way to get SSL between apache and tomcat, is to use mod_proxy
Filip
c. wrote:
Thanks Filip,
We've always had the need for SSL, and our config worked without any
changes
when I put AJP in the mix. It doesn't,
Thanks Filip,
We've always had the need for SSL, and our config worked without any changes
when I put AJP in the mix. It doesn't, however, work with proxy http.
On 3/23/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
in my last email I forgot one
SSLProxyMachineCertificateFile <--
SSL
in my last email I forgot one
SSLProxyMachineCertificateFile <--
SSLProxyEngine
SSLProxyMachineCertificatePath
SSLEngine
SSLProxyProtocol,
SSLProxyCipherSuite
c. wrote:
Filip, thanks for the info, I'll listen to anyone with good advice.
So you
recommend mod_proxy_http over mod_jk?
Is it the
c. wrote:
Filip, thanks for the info, I'll listen to anyone with good advice.
So you
recommend mod_proxy_http over mod_jk?
Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it doesn't give
much info.
Ah, it's straight f
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
c. wrote:
Filip, thanks for the info, I'll listen to anyone with good advice. So you
recommend mod_proxy_http over mod_jk?
That's a good question. In two successive messages, he recommended each
over the
no worries, mistakes happen.
Thanks for the clarification on the jk exceptions. Now that you've said it
it seems obvious.
I can get mod_proxy_http to work unsecurely, but once I hit the secure pages
I get internal server error. Why would I not have had to do anything to
enable ssl with mod_pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
Apologies to all. I read mod_proxy_http as mod_proxy_ajp, and made a
fool of myself. Duh.
- -chris
Christopher Schultz wrote:
> Chris,
>
> c. wrote:
>> I'll try upping the connection timeouts, but aside from the problem
>> of dropped connectio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
c. wrote:
> Filip, thanks for the info, I'll listen to anyone with good advice. So you
> recommend mod_proxy_http over mod_jk?
That's a good question. In two successive messages, he recommended each
over the other.
> Is it the same basic se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
c. wrote:
> I'll try upping the connection timeouts, but aside from the problem
> of dropped connections what I'm really confused about is why there is
> a jk exception
> (org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518))
> w
Filip, I know this isn't the httpd forum, but how did you get the ssl
working using mod_proxy_http?
Chris.
On 3/23/07, c. <[EMAIL PROTECTED]> wrote:
Filip, thanks for the info, I'll listen to anyone with good advice. So
you recommend mod_proxy_http over mod_jk?
Is it the same basic setup as
Filip, thanks for the info, I'll listen to anyone with good advice. So you
recommend mod_proxy_http over mod_jk?
Is it the same basic setup as mod_proxy_ajp? Looking at the doc (
http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it doesn't give
much info.
c.
On 3/23/07, Filip Hanik -
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
I'd recommend moving to mod_proxy_http, it will be easier for you to debug.
Bah! :(
that sounds knowledgeable :)
the error below seems to be more of a problem with a
On top of the previous error in the log tomcat log file, the following error
shows up in the httpd error log:
[Thu Mar 22 19:55:23 2007] [error] (70007)The timeout specified has expired:
ajp_ilink_receive() can't receive header
[Thu Mar 22 19:55:23 2007] [error] ajp_read_header: ajp_ilink_receive
Looking at the server.xml connectionTimeout, I've set the value to 60,
600 seconds not 60 seconds, could I be holding onto the connection for too
long? The reason I'm asking is 'cause I don't think adding another five
seconds to the 600 will make a difference, adding five seconds to 60 could
I'll try upping the connection timeouts, but aside from the problem of
dropped connections what I'm really confused about is why there is a jk
exception (org.apache.jk.common.ChannelSo
cket.send(ChannelSocket.java:518)) when I'm using mod_proxy_ajp, NOT
mod_jk.
Chris.
On 3/23/07, Christop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin,
Martin Gainty wrote:
> broken pipe means that at one end (more than likely the DB listener you're
> connecting to somehow dropped)
Unlikely:
>> java.net.SocketException: Broken pipe
>>at java.net.SocketOutputStream.socketWrite0(Native M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
> I'd recommend moving to mod_proxy_http, it will be easier for you to debug.
Bah! :(
> the error below seems to be more of a problem with apache (mod_proxy_ajp)
> then with tomcat, tomcat is simply trying to wr
ou de le reproduire.
- Original Message -
From: "c." <[EMAIL PROTECTED]>
To:
Sent: Friday, March 23, 2007 12:47 PM
Subject: Tomcat mod_proxy_ajp and jk exceptions
> Hello,
>
> I'm using mod_proxy_ajp as my link b/w tomcat and apache. Things are
> working w
I'd recommend moving to mod_proxy_http, it will be easier for you to debug.
the error below seems tobe more of a problem with apache (mod_proxy_ajp)
then with tomcat, tomcat is simply trying to write a message, but the
connection is no longer valid.
Filip
c. wrote:
Hello,
I'm using mod_prox
Hello,
I'm using mod_proxy_ajp as my link b/w tomcat and apache. Things are
working well with the exception of getting the following error:
2007-03-22 20:02:42,875 [TP-Processor51] WARN
org.apache.jk.core.MsgContext - Error sending end packet
java.net.SocketException: Broken pipe
at java.net
30 matches
Mail list logo
