RE: RE: Having issues trying to use rewriterule,proxypass,proxyreversepass

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tom,

I put port# in to indicate that we are using a different port than standard on the inside network/server.
In this case it is an Oracle SOA server on port 7011.
I can assure you that none of my actual rules contains or begins with a # sign.

I'm still not sure why my rewrite rules are not working and have been banging on this for a few days now.

Scott

> i.e. https://myserver.mydomain.com/dir1/dir2/login.jspx gets proxied 
> to http://internalserver.mydomain.com:port#/dir1/dir2/login.jspx

Anything after a '#' in a URL is browser state, the browser neither sends nor receives this data from a server.

It's also the comment character in httpd config files, so god knows what that rule does.

Cheers

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx





[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux