As I move over to a new server at home, I am left with a legacy
java/tapestry financial application I wrote some while ago and which
would be a pain to relearn to change anything (since I am about to
rewrite it anyway). Since it runs under tomcat just fine on the
original server, I am trying
Alan Chandler wrote:
...
I was under the impression the mod_proxy_http was supposed to fix this up.
...
How do I get mod_proxy_html to correct this base href code?
I figured this out. I was mixing up mod_proxy_http and mod_proxy_html
Sorry for the noise
.
I am wondering if when I rewrite, I need to do something with the host
name.
Or just google for the error response message.
//frank
27 aug 2007 kl. 08.49 skrev Alan Chandler:
On Wednesday 22 Aug 2007, Alan Chandler wrote:
I am running Debian Etch Apache2 with Tomcat backending
On Wednesday 22 Aug 2007, Alan Chandler wrote:
I am running Debian Etch Apache2 with Tomcat backending it connected
via the standard Debian libapache2-mod-jk package.
Something has happened (a Debian upgrade maybe) that has made it stop
working properly. It has been working
Accessing http
]
[www.chandlerfamily.org.uk/sid#83d7940][rid#860ee88/initial] (2)
forcing '/blog/a
pp' to get passed through to next API URI-to-filename handler
and my access log shows that url being accessed, but no other evidence.
Can anyone see what I am doing wrong, or how I could debug it
--
Alan Chandler
http
protocol and which port.
The reason I need to know, is that I currently map port 443 to a completely
different space, mapping over an internal virtual host to support webmail.
Can someone give me a clear summary of this?
--
Alan Chandler
http://www.chandlerfamily.org.uk
Open Source. It's
