On Fri, Jul 26, 2013 at 02:59:00PM +0100, Giles Coochey wrote:
> OK, but I should still expect the warnings at startup?
At startup? The same warnings?
> I've done a packet capture and noted that I have all these headers set:
>
> X-Forwarded-For: (a comma seperated list of IPs, original client a
On 26/07/2013 14:09, Kevin Falcone wrote:
On Fri, Jul 26, 2013 at 01:23:32PM +0100, Giles Coochey wrote:
I run RT (upgraded to 4.0.15 today), but this is a small issue I've
always had with my set up.
I always get the following in my apache errorlogs:
You should get these once per process start
On 26/07/2013 14:09, Kevin Falcone wrote:
On Fri, Jul 26, 2013 at 01:23:32PM +0100, Giles Coochey wrote:
I run RT (upgraded to 4.0.15 today), but this is a small issue I've
always had with my set up.
I always get the following in my apache errorlogs:
You should get these once per process start
On Fri, Jul 26, 2013 at 01:23:32PM +0100, Giles Coochey wrote:
> I run RT (upgraded to 4.0.15 today), but this is a small issue I've
> always had with my set up.
>
> I always get the following in my apache errorlogs:
You should get these once per process startup, yes?
> [Fri Jul 26 09:05:14 2013
Hi,
I run RT (upgraded to 4.0.15 today), but this is a small issue I've
always had with my set up.
I always get the following in my apache errorlogs:
[Fri Jul 26 09:05:14 2013] [warning]: The requested port (80) does NOT
match the configured WebPort (443). Perhaps you should Set($WebPort,
