On Mon, 2017-02-20 at 11:56 +0300, Marat Khalili wrote:
> It's very insightful, but what other _general purpose_ tool do we have
> here? Correct me if I'm wrong, but seems like URL rewrite C (let alone
> Python) is not yet created.
Wrong question.
URL rewriting isn't a problem you look to solv
On 20/02/17 11:01, Nick Kew wrote:
it's commonly used as a hacked-up
scripting language comprisising just two main instructions
(single IF aka RewriteCond, and GOTO aka RewriteRule) with
side-effects. [...]
By analogy, when I got my first programming job in the 1980s,
there was still lots of anci
On Sun, 2017-02-19 at 20:27 +0300, Marat Khalili wrote:
> "When not to use mod_rewrite" page was probably written by people
> frustrated with too many examples of incorrect mod_rewrite
> configurations in this forum.
Actually it was largely written by the same people who wrote the
mod_rewrite doc
Just a personal opinion: mod_rewrite is perfectly fine as long as you know it
well, and any Apache admin will have to learn and use it eventually. If you can
accomplish your task with one powerful module you already know, learning
"simpler" modules and enabling them on your server is both silly
Most of my hosts are HTTPS only - I do have one host that allows port 80
for a yum package repository, https isn't needed there because the
packages themselves are signed and yum validates them on the client side
before installing.
This is an example of what I do:
ServerName librelamp.com
Re
Sorry to butt in here. I've been following this post with some interest.
I wanted to accomplish the same thing the original OP wanted to
accomplish, redirect all traffic to the secure version of my site. I went
to the internet and found directions on how to do this using mod_rewrite
rules.
As I only run HTTPS - I have the following on port 80 - (this can't be
done with redirect)
...
...
...
RewriteEngine on
RewriteCond %{REQUEST_URI} !^/.well-known/acme-challenge
RewriteRule ^(.*)$ https://%{SERVER_NAME}%{REQUEST_URI}
[R=permanent,L,NE]
So I only have one po
Yes please, let's stay away of convoluted and most times innecessary
mod_rewrite examples to do simpleton configurations.
If you are in virtualhost 80, you have specified servername correctly and
you just want to redirect to ssl, why not a single Redirect statement?
As Yann's refered document say
> Date: Saturday, February 18, 2017 11:04:34 -0700
> From: James Moe
>
> On 02/18/2017 05:08 AM, Rodrigo Cunha wrote:
>> i want redirect all request from port 80 to 443.
>> what is better setting for fix this?
>>
> Better than what?
> Fix? Is it broken?
>
> RewriteCond %{HTTP_HOST} =www.ex
My redirect and my website is work in https port but my webserver not
display the styles maked in css.
Do you help-me?
2017-02-18 16:04 GMT-02:00 James Moe :
> On 02/18/2017 05:08 AM, Rodrigo Cunha wrote:
> > i want redirect all request from port 80 to 443.
> > what is better setting for fix th
On 02/18/2017 05:08 AM, Rodrigo Cunha wrote:
> i want redirect all request from port 80 to 443.
> what is better setting for fix this?
>
Better than what?
Fix? Is it broken?
RewriteCond %{HTTP_HOST} =www.example.com
RewriteCond %{SERVER_PORT} =80
RewriteRule ^(.*)$ https://www.example.com/$1 [
Hi,
On Sat, Feb 18, 2017 at 1:08 PM, Rodrigo Cunha
wrote:
> Dears, i want redirect all request from port 80 to 443.
> what is better setting for fix this?
https://httpd.apache.org/docs/2.4/rewrite/avoid.html#redirect
-
To unsub
Dears, i want redirect all request from port 80 to 443.
what is better setting for fix this?
--
Atenciosamente,
Rodrigo da Silva Cunha
São Gonçalo, RJ - Brasil
13 matches
Mail list logo
