Re: [users@httpd] am i hacked ?

On 2/6/2017 8:36 AM, Jack Swan wrote: > What upsets me is that these two requests have statuscode 200, which mean it > was successfull. As Jonesy points out, it's normal for the web server to simply ignore a request's query-string in a request where it wouldn't mean anything. So Apache is happ

Re: [users@httpd] Apache mod_dav alternatives?

On May 21, 2016, at 2:08 PM, Bjoern Voigt wrote: > I am using Apache as a web and proxy server, but I am unhappy with > Apache as a WebDAV file server. > > I am missing a good file permission or ACL configuration in Apache mod_dav. It's relatively easy to write a custom authz provider for your

Re: [users@httpd] Apache permissions stabs new Linux user in face with icepick. Suggestions?

On Mar 9, 2016, at 6:38 PM, Francis Roy wrote: > Thank you that answers my question quite nicely. It's not a giant flag waving > at the internet, but if someone got a hold of my machine directly, it could > provide a small bit of information used in a general strategy. Right. It's not automati

Re: [users@httpd] setfib: NO: invalid FIB (max 0) FreeBSD 9.3 64bit

On Sep 9, 2015, at 3:42 PM, Kurtis Rader wrote: > On Wed, Sep 9, 2015 at 10:45 AM, Motty > wrote: > Starting apache22. > setfib: NO: invalid FIB (max 0) > > That's not an Apache HTTPD config option. Googling for "setfib invalid fib" > yields a bunch of results that

Re: [users@httpd] Forcing 256-bit AES encryption on server

On 23 Jul 2014, at 7:25 AM, Slusar,Michael wrote: > Does anyone know how to set up SSL options in httpd.conf or ssl.conf? I am > trying to force the server to use 256-bit AES Encryption when the > client\server hello handshake is performed. You can control the set of ciphers that the server is

Re: [users@httpd] Serve web pages from a different server

On 16 Jul 2014, at 5:17 PM, John Garrett wrote: > Is there a way to use the virtual server directive to serve web pages from a > different server with a different IP address than my production > FreeBSD/Apache box? > > I have DNS set up so website1.com and website2.com both resolve to the > machi

[users@httpd] Multilingual ErrorDocuments vs. content-type negotiation

I'm having an annoying problem as a result of enabling multilingual error documents. The situation is this: - I'm using the multilingual error docs that come with apache 2.4.x. - I have clients other than web browsers --- API consumers, WebDAV clients, etc. --- which don't include text/html