Actually this is better:
RewriteCond %{HTTPS} !on
RewriteRule .* https://webmail.example.com [R,L]
On Nov 21, 2011 8:48 AM, "Igor Cicimov" wrote:
> Try this one
>
> RewriteCond %{HTTP_PORT} !443
> RewriteRule .* https://webmail.example.com
> On Nov 21, 2011 3:15 AM, "David Mehler" wrote:
>
>> H
Try this one
RewriteCond %{HTTP_PORT} !443
RewriteRule .* https://webmail.example.com
On Nov 21, 2011 3:15 AM, "David Mehler" wrote:
> Hello,
>
> I've got a rewrite question. I'm running webmail on
> webmail.example.com and I've got that secured by ssl. If I go to:
>
> https://webmail.example.co
I have a lot more of the following in my daily log. Any idea what
exactly the known hack attempt was?
> Attempts to use known hacks by 197 hosts were logged 562 time(s) from:
71.198.234.91: 14 Time(s)
66.169.235.10: 10 Time(s)
A total of 197 sites probed the server
108.201.92.73
Hello,
I've got a rewrite question. I'm running webmail on
webmail.example.com and I've got that secured by ssl. If I go to:
https://webmail.example.com
it works. But as a user if they go to either of:
http://webmail.example.com
or just:
webmail.example.com
without the protocol it doesn't. I
On Sun, Nov 20, 2011 at 5:01 AM, Gadi Katsovich wrote:
> Hello All,
>
> We’re trying to set up an Apache server that would serve requests for large
> static files (500MB).
>
> We use AliasMatch to match the request url to the actual path.
>
> It works fine when no caching is involved.
>
> However,
Hello All,
We're trying to set up an Apache server that would serve requests for large
static files (500MB).
We use AliasMatch to match the request url to the actual path.
It works fine when no caching is involved.
However, when we do use caching, we get memory leaks the size of the served
files.