gt; Redirect doesn't allow you to distinguish between 301s and 302s which you
>> can do with mod_rewrite {very useful feature tbh when it comes to bits like
>> this} - the user is using WordPress so will almost certainly be using
>> mod_rewrite to handle the nice URLs...
is using WordPress so will almost certainly be using
>> mod_rewrite to handle the nice URLs
>>
>> As for the issue without a server name - you don't need one in the 800
>> unless you are doing something clever - as for the redirects it doesn't
>> brea
t; you can put one in - just make sure that it is included first!
> -Original Message-
> From: Frank
> Sent: 12 October 2020 18:10
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] Forwarding IP to HTTPS. [EXT]
>
> James,
>
> Unless the user has many hosts,
ut
> you can put one in - just make sure that it is included first!
> -Original Message-
> From: Frank
> Sent: 12 October 2020 18:10
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] Forwarding IP to HTTPS. [EXT]
>
> James,
>
> Unless the user h
V3OmOKQ_c29so3_jWrThxEfgCkxLIfX3sIvw&s=mw3MrVOeeCL66Y
> rcxABO8NMrnnmzLmHQBeAdm0m8VYA&e=
>
> ## Do not use Server Alias here for alternative domains - only use
> for test/dev sites...
>
> DocumentRoot /var/www/wp
>
>
>
> Options Indexes FollowSymL
>
>
>
> Options Indexes FollowSymLinks
>
> AllowOverride all
>
> Require all granted
>
>
>
>
>
> ## Put the rest of your wordpress stuff here...
>
>
>
>
>
> *From:*Jason Long
> *Sent:* 12 October 2020 16:39
> *To:* use
t; manner rather than just dropping the
> requests on the floor
>
>
> -Original Message-
> From: Frank
> Sent: 12 October 2020 16:36
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] Forwarding IP to HTTPS. [EXT]
>
> James,
>
> Omi
## Put the rest of your wordpress stuff here...
From: Jason Long
Sent: 12 October 2020 16:39
To: users@httpd.apache.org
Subject: Re: [users@httpd] Forwarding IP to HTTPS. [EXT]
Excuse me,
Can you clean my configuration?
On Monday, October 12, 2020, 07:06:17 P
org
Subject: Re: [users@httpd] Forwarding IP to HTTPS. [EXT]
Excuse me,
Can you clean my configuration?
On Monday, October 12, 2020, 07:06:17 PM GMT+3:30, Frank
mailto:thu...@apache.org>> wrote:
James,
Omitting an explicit ServerName in name-based vhosts is a bad idea as
well. You ca
equests on the floor
-Original Message-
From: Frank
Sent: 12 October 2020 16:36
To: users@httpd.apache.org
Subject: Re: [users@httpd] Forwarding IP to HTTPS. [EXT]
James,
Omitting an explicit ServerName in name-based vhosts is a bad idea as well. You
can create conflicts or ambigu
Excuse me,Can you clean my configuration?
On Monday, October 12, 2020, 07:06:17 PM GMT+3:30, Frank
wrote:
James,
Omitting an explicit ServerName in name-based vhosts is a bad idea as
well. You can create conflicts or ambiguities.
On 12/10/20 11:22 AM, James Smith wrote:
> This would
James,
Omitting an explicit ServerName in name-based vhosts is a bad idea as
well. You can create conflicts or ambiguities.
On 12/10/20 11:22 AM, James Smith wrote:
> This would be my set-up in your case - note as someone said it was too
> complex I've removed the extra security bits I'd left i
t vhost as a default for
>>> http://ip/ requests, define another.
>>>
>>> On 12/10/20 10:26 AM, Jason Long wrote:
>>>> Thank you.
>>>> I added that lines to my Virtual Host file but it show me "Your
> connection is not private".
>
>>> On 12/10/20 10:26 AM, Jason Long wrote:
>>>> Thank you.
>>>> I added that lines to my Virtual Host file but it show me "Your
> connection is not private".
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
&g
gt;>
>>>
>>>
>>> On Monday, October 12, 2020, 05:16:27 PM GMT+3:30, James Smith
>>> wrote:
>>>
>>>
>>>
>>>
>>>
>>> Yes - with Apache you put a default virtual host which redirects all
>>> tra
This would be my set-up in your case - note as someone said it was too complex
I've removed the extra security bits I'd left in by accident...
## Port 80 && 443 default configs...
RequestHeader unset X-is-ssl
RewriteEngine on
RewriteRule ^(.*)$ https://www.mydomain.com%{REQUEST_
e".
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Monday, October 12, 2020, 05:16:27 PM GMT+3:30, James Smith
>>> wrote:
>>>
>>>
>>>
>>>
>>>
>>> Yes - with Apache you put a default v
t;
>> Yes - with Apache you put a default virtual host which redirects all traffic
>> to your https server
>>
>>
>> RequestHeader unset X-is-ssl
>>
>>
>> Require all denied
>>
>> Require all granted
>>
>> ProxyPreserv
rver
>>
>>
>> RequestHeader unset X-is-ssl
>>
>>
>> Require all denied
>>
>> Require all granted
>>
>> ProxyPreserveHost on
>> RewriteEngineon
>> RewriteRule ^(.*)$ https://myservername
>
> ProxyPreserveHost on
> RewriteEngine on
> RewriteRule ^(.*)$ https://myservername.com%{REQUEST_URI}
>[R=permanent,L,NE]
>
>
> You can do something for 443 as well.
>
> -----Original Message-
> From: Jason Long
> Sent: 12 October 2020
> [R=permanent,L,NE]
>
>
> You can do something for 443 as well.
>
> -Original Message-----
> From: Jason Long
> Sent: 12 October 2020 14:10
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] Forwarding IP to HTTPS. [EXT]
>
> Thank you.
rom: Jason Long
Sent: 12 October 2020 14:10
To: users@httpd.apache.org
Subject: Re: [users@httpd] Forwarding IP to HTTPS. [EXT]
Thank you.
I want when a user enter my server IP address in his\her browser then it
forward to
"https://urldefense.proofpoint.com/v2/url?u=https-3A__mywebsite
%{REQUEST_URI}
[R=permanent,L,NE]
You can do something for 443 as well.
-Original Message-
From: Jason Long
Sent: 12 October 2020 14:10
To: users@httpd.apache.org
Subject: Re: [users@httpd] Forwarding IP to HTTPS. [EXT]
Thank you.
I want when a user enter my server IP address in his\her
23 matches
Mail list logo