Hello,
mod_wl has some advantages, mod_proxy does not support i.e. mod_proxy does
normally only a ping to check if a backend server is available, which normally
works in 99% even if the web-application behind is not available, so it is
possible that mod_proxy routes the request to /backend even
2015-02-08 21:15 GMT+01:00 Yann Ylavic :
> On Sun, Feb 8, 2015 at 9:03 PM, Yann Ylavic wrote:
> > On Sun, Feb 8, 2015 at 7:36 AM, YUSUI T
> wrote:
> >>
> >> root@hostname:~# tail -n 6 /etc/apache2/mods-available/ssl.conf
> >>
> >> ServerName www.mydomain.com
> >> Redirect / http
2015-02-09 2:22 GMT+01:00 Todd Simons :
> Hello All
> We've been using the generic mod_proxy for years. We utilize Apache to
> layer in HTTPS from the world into our DMZ, then utilize
> proxypass/proxypassreverse to our internal servers. Our internal servers
> vary between iis, weblogic, tomcat
Hello All
We've been using the generic mod_proxy for years. We utilize Apache to
layer in HTTPS from the world into our DMZ, then utilize
proxypass/proxypassreverse to our internal servers. Our internal servers
vary between iis, weblogic, tomcat, and a few others.
mod_proxy has been working gre
On Sun, Feb 8, 2015 at 9:03 PM, Yann Ylavic wrote:
> On Sun, Feb 8, 2015 at 7:36 AM, YUSUI T wrote:
>>
>> root@hostname:~# tail -n 6 /etc/apache2/mods-available/ssl.conf
>>
>> ServerName www.mydomain.com
>> Redirect / https://www.mydomain.com/
>>
>
> You probably want to redirec
On Sun, Feb 8, 2015 at 7:36 AM, YUSUI T wrote:
>
> root@hostname:~# tail -n 6 /etc/apache2/mods-available/ssl.conf
>
> ServerName www.mydomain.com
> Redirect / https://www.mydomain.com/
>
You probably want to redirect to https when the request is plain http, hence :
above.
-
> Server should be SSL-aware but has no certificate configured [Hint:
> SSLCertificateFile] ((null):0)
> [Sun Feb 08 13:31:27.595849 2015] [ssl:emerg] [pid 7124] AH02312:
> Fatal error initialising mod_ssl, exiting.
Are you sure you have a cert configured? Double check ssl config
---
HTML 4.01 and XHTML 1.0 don't support the data- attributes since they were
added in HTML5, so striping them out is the correct behavior.
If that is not what you want it to do, don't set that directive.
- Y
On Sun, Feb 8, 2015 at 12:15 PM, A. Lotfi
wrote:
> Hi,
>
> I am not an Apache expert, I a
Hi,
I am not an Apache expert, I am just a java and html developer, I wrote lot of
code using html data attributes, but I was surprised that Apache swallow are
strip them, I went to this page :
mod_proxy_html - Apache HTTP Server Version 2.4
| |
| | | | | | | |
| mod_proxy_html
I found the problem, but can't explain it.
In my original site-specific .conf file I had a directory block giving
access to a directory that does not exist. It was a holdover from the
old system that was not duplicated/replicated on the new one. The odd
thing is that Apache didn't complain about t
2015-02-08 20:30 GMT+09:00 Chris Arnold :
> You probably could have left that entry in and just added the Redirect
> statement (not sure what flavor of OS you are using).
OS I am using is Ubuntu 14.04.1 LTS (GNU/Linux 2.6.32-042stab093.5 x86_64).
> root@hostname:~# tail -n 6 /etc/apache2/mods-a
I've set up apache 2.2 and mod_security 2 on a centos 6 machine. As
you know mod_security produces it's own kind of error log file which
it's output is something like :
[Sun Feb 08 13:53:25 2015] [error] [client 192.168.22.90] ModSecurity:
[file
"/etc/httpd/conf.d/mod_security2/base_rules/modsec
On Feb 8, 2015, at 1:38 AM, YUSUI T
mailto:yusui.tomik...@gmail.com>> wrote:
The error.log says nothing.
Next, I exchanged for the "Redirect". But it shows the
following errors.
You probably could have left that entry in and just added the Redirect
statement (not sure what flavor of OS you
13 matches
Mail list logo
