Awesome explanation Matt!
El mar., 29 ene. 2019 a las 19:36, Muggeridge, Matt
() escribió:
>
> ProxyPassReverse is used for rewriting response headers related only to
> redirection. As per the docs, it affects only “Location”,
> “Content-Location” and “URI” headers on HTTP redirect responses.
Maybe related to using a name instead of an ip address with Listen
directive. IMO using names with Listen directive is a terrible idea,
documentation of Listen directive specifies you should use ip address
too. Is that name correctly resolving to the specific ip address in
the system?
El mar., 5
This was the bit I was missing! Thanks!
--Tom Noonan II
On Wed, Feb 6, 2019 at 3:45 PM Eric Covener wrote:
> On Wed, Feb 6, 2019 at 3:38 PM Tom Noonan wrote:
> >
> > Good afternoon:
> >
> > I've written a custom Apache2 module and I'm having some difficulty with
> logging. Logging is
Directory / is the root of the filesystem, so it should always be set
in server config with Require all denied, it is not the documentroot,
chances are you have a Directory directive elsewhere denying, also
make 100% sure you don't mix Order/Allow/Deny with 2.4 directives.
So:
Server config
On Wed, Feb 6, 2019 at 3:38 PM Tom Noonan wrote:
>
> Good afternoon:
>
> I've written a custom Apache2 module and I'm having some difficulty with
> logging. Logging is working as expected using the global log level. For
> example, if I set the following I get debug logs from my module:
>
>
Good afternoon:
I've written a custom Apache2 module and I'm having some difficulty with
logging. Logging is working as expected using the global log level. For
example, if I set the following I get debug logs from my module:
LogLevel Debug
However, if I attempt to set the loglevel for only
Hallo,
ich habs: ohne darauf zu achten, hatte ich einen zweiten Virtualhost
eingerichtet, der von domain.tld auf www.domain.tld weiterleitete. Dort
muss aber auch das Zertifikat eingebunden werden, was ich übersah.
Manfred
Am 06.02.19 um 13:15 schrieb Manfred Rebentisch:
> Hallo,
> ich habe bei
Hallo,
ich habe bei einer Domain ein merkwürdiges Problem. Der Browser meldet:
Fehlercode: SSL_ERROR_RX_RECORD_TOO_LONG
Der Server ist Debian Jessie (mit backports), Der Apache hat die Version
2.4.10-10+deb8u13
Installiert sind:
Paket: libgnutls-openssl27
Version: 3.3.30-0+deb8u1
Paket:
Hello Dan,
On Wed, 6 Feb 2019 at 13:05, Dan Ehrlich wrote:
>
> Looks like you just need to enable mod_headers
> (http://httpd.apache.org/docs/current/mod/mod_headers.html) and then add the
> below text that they mention in the Stack Over question?
>
> You might need to run “a2enmod headers”
