OK - thanks to your input I was able to get a look at the sorce code
on the real server and it is littered with absolute URLs.
My proxy statements were valid I was able to append the proxy server
URL string with the URLs and it dished up the content with no issues.
I will take a look at the oth
Also take a look at this
http://httpd.apache.org/docs/2.2/mod/mod_ext_filter.html
It can be used for writing an output filter.
On 9/29/06, Serge Dubrouski <[EMAIL PROTECTED]> wrote:
If I'm right about absolute links the best way to fix that is make
your backend server to produce relative links
If I'm right about absolute links the best way to fix that is make
your backend server to produce relative links only, i.e. without
server name.
Other way is writing a special handler that would parse all aoutgoing
data and strip the name of backend servere from the links. Of course
it will lead
Hmmm, interesting. So how do I get around this? I am perplexed to say
the least...
On 9/29/06, Serge Dubrouski <[EMAIL PROTECTED]> wrote:
I've tested kind of your configuration and everything works all right
in mine test environment. So I still think that your real server
(Oracle Application Se
I've tested kind of your configuration and everything works all right
in mine test environment. So I still think that your real server
(Oracle Application Server) somehow generates absolute (not realive)
links. I'm almost sure in that.
On 9/29/06, Jeff DeFord <[EMAIL PROTECTED]> wrote:
AFAIK, it
No, this is not an attempt at redirection. The real server URL's are
not meant to be seen. All html should all appear as if it originated
from the proxy server.
The base (root-level) URLs are already working in this manner. The
URLs that include additional directory structures beyond "/" are not
So you want the proxy server to redirect https request to the real server. Your real serveris not hide behind the proxy. The client browsers can access the real server directly if
the url of the real server is known. The https session between client browser and the real server is established after
Honestly I'm not really familiar with ProxyPass and ProxyPassReverse.
I would do following:
RewriteRule ^/(.*)$https://real_server:8050/$1 [P,L]
Try to put that instead of your ProxyPass and ProxyPassReverse. That
should do the trick.
On 9/29/06, Jeff DeFord <[EMAIL PROTECTED]> wrote:
AFA
AFAIK, it is all static content with some jsp pages. No CGI/PHP/Etc...
The real server is an Oracle application server, so all of the web
content was derived from the installation process script "AutoConfig".
My confusion is in trying to get the URL's rewritten and proxied that
go beyond the root
What kind of "real" server do you have on backend? Does it have static
content or dynamic? Could it be that your wrong links are generated on
backend by PHP/ASP/CGI or any other dynamic application that uses
$SEVER_NAME or some other variable to build absolute links?
On 9/28/06, Jeff DeFord <[EMA
For testing purposes, I'm using a self-signed sert on the proxy server
for the initial redirection, then the proxy server acts as a SSL
client for all proxied requests that are handed off to the app server
which is listening on port 8050 (SSL) using a real certificate.
I copied the real cert file
Where is your server cert installed? If it is installed on the reverse proxy server, do you decrypte the incoming HTTPS traffic and re-encrypte it again in the proxy server before sending it to the next host?
On 9/28/06, Jeff DeFord <[EMAIL PROTECTED]> wrote:
Not sure if that would work since all
Not sure if that would work since all requests are HTTPS...
Can you elaborate?
Here are the modules I compiled in when I built Apache:
# ./httpd -l
Compiled in modules:
core.c
mod_access.c
mod_auth.c
mod_log_config.c
mod_headers.c
mod_setenvif.c
mod_proxy.c
proxy_connect.c
proxy_ftp.c
p
Did you try HTTP Connect?
>>> [EMAIL PROTECTED] 9/27/2006 10:35 AM >>>
All:
I have some questions regarding the way to implement
Apache as a reverse proxy server using mod_rewrite in order to mask the
real
URLs. Users will connect to the proxy, then the proxy will connect to
the real server that
All:
I have some questions regarding the way to implement
Apache as a reverse proxy server using mod_rewrite in order to mask the real
URLs. Users will connect to the proxy, then the proxy will connect to
the real server that is listening on port 8050 (SSL)
So far this is what I have working:
15 matches
Mail list logo
