ProxyPass /webapp/ https://sub.example.com/webapp/
ProxyPassReverse /webapp/ https://sub.example.com/webapp/
RedirectMatch ^/$ https://sub.example.com/webapp/
# Redirect iFolder and Admin to HTTPS
Redirect /webapp2 https://example.com/webapp2
Redirect /webapp3 https://exam
you can Redirect / to https://domain/share/
RedirectMatch is to use regular expressions, pcre.
Please read the different uses at:
http://httpd.apache.org/docs/current/mod/mod_alias.html
El Thu Jan 29 2015 at 13:37:15, Chris Arnold ()
escribió:
> Don't use pcre in redirect.
>
> For what you ask
Don't use pcre in redirect.
For what you ask you just need a simple:
Redirect / https://yourdomain/ in the nonssl virtual host.
If you insist on using pcre with redirect for some particular reason you have
not mentioned yet, use RedirectMatch.
Won't that redirect all traffic? I only need to red
Don't use pcre in redirect.
For what you ask you just need a simple:
Redirect / https://yourdomain/ in the nonssl virtual host.
If you insist on using pcre with redirect for some particular reason you
have not mentioned yet, use RedirectMatch.
Regards
El jue., 29 de enero de 2015 1:06, Chris A
On Jan 28, 2015, at 6:31 PM, Yehuda Katz
mailto:yeh...@ymkatz.net>> wrote:
Make sure you put these in the correct VHOST. They need to be in the :80 vhost,
not the :443 vhost.
I usually use the Redirect directive
(http://httpd.apache.org/docs/2.4/mod/mod_alias.html#redirect) instead.
Yea, I t
Make sure you put these in the correct VHOST. They need to be in the :80
vhost, not the :443 vhost.
I usually use the Redirect directive (
http://httpd.apache.org/docs/2.4/mod/mod_alias.html#redirect) instead.
- Y
On Wed, Jan 28, 2015 at 4:55 PM, Chris Arnold
wrote:
> Apache 2.4.10 on SLES 12
Hi,
Solved :-)
Actually the problem was not in this dashboard new rule, the problem was in
one of the previous rules that was skipping my new rule in some cases.
So after I changed the rule order the final solution is:
RewriteCond %{HTTPS} !=on
RewriteRule ^/dashboard$ https://%{HTTP_HOST}/dash
Assuming there is additional URL coming after /dashboard when the server
sends you the login page...
e.g. /dashboard/login.php
...Your redirect will not match with the $ at the end of the condition...
RewriteRule ^/dashboard$ https://%{HTTP_HOST}/dashboard [R=301,L]
says /dashboard, so /dashboa
On Tue, Apr 16, 2013 at 10:07 AM, Igor Cicimov wrote:
> There shouldnt be empty line between these two.
>
Hi Igor,
In the conf file there isn't empty line between then:
RewriteCond %{HTTPS} !=on
RewriteRule ^/dashboard$ https://%{HTTP_HOST}/dashboard [R=301,L]
and I got the same problem after
On 16/04/2013 10:17 PM, "Felipe Roman" wrote:
>
> Hi Igor,
>
> Thanks for your help. I replaced the %{SERVER_NAME} by %{HTTP_HOST} but
the behavior continue the same. The redirect worked fine when I access
> http://myhost.com/dashboard I got redirected to
https://myhost.com/dashboard
>
> but after
Hi Igor,
Thanks for your help. I replaced the %{SERVER_NAME} by %{HTTP_HOST} but the
behavior continue the same. The redirect worked fine when I access
http://myhost.com/dashboard I got redirected to https://myhost.com/dashboard
but after the redirect the login page does not work anymore... even
RewriteRule ^/dashboard$ https://%{HTTP_HOST}/dashboard [R=301,L]
On 16/04/2013 7:58 AM, "Felipe Roman" wrote:
> Hi,
>
> I'm trying to configure a specific application (developed in
> Python/Django) to run only through HTTPS, what I need is redirect a
> specific directory to HTTPS:
>
> FROM
>
> h
12 matches
Mail list logo
