d even the apache docs are a pin to decipher as far as I
am concerned.
Scott
-Original Message-
From: Tom Evans [mailto:tevans...@googlemail.com]
Sent: Monday, February 10, 2014 8:48 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] RE: Having issues trying to use
rewriterule
On Mon, Feb 10, 2014 at 4:39 PM, Riggen, Scott
wrote:
> 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 w
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 wor
On Fri, Feb 7, 2014 at 11:04 PM, Riggen, Scott
wrote:
> Current configuration in my vhosts file.
>
>
>
> This is not in a location or directory block. It is in the normal
> virtualhost block
>
> I want my first rewriterule setup so that a user can type in
> https://myserver.mydomain.com/ and it w
]
Sent: Friday, February 07, 2014 11:12 AM
To: users@httpd.apache.org
Subject: [users@httpd] RE: Having issues trying to use
rewriterule,proxypass,proxyreversepass
Well. A couple of days now and still no closer to making this work.
I'm sure I am missing something obvious. Time to pour over al
Well. A couple of days now and still no closer to making this work.
I'm sure I am missing something obvious. Time to pour over all the apache docs
line by line since I have not found anything relevant via google or bing.
Or maybe switch to another web server other than apache..
Scott
From:
