Somehow, my recent upgrade to Ubuntu 20.04 switched the Apache MPM module installed and thus disabled HTTP2 for PHP requests on my server.Continue reading post "#2889"
If you’re routing requests for script file names through FastCGI, and don’t have some rule to catch requests for unknown scripts, you might find errors like:
Got error 'Primary script unknown\n'
in your error log.Continue reading post "FastCGI and “Primary Script Unknown”"
Up way later than I wanted to be, fighting with Symfony’s framework bundle trapping PHP errors from getting to my Apache logs, and Apache’s
ErrorLogFormat not being able to display
REQUEST_URI. Gonna have to come back to these later.
Looking at a page discussing the code of the first web browser (WorldWideWeb), I noticed a line designating port 2784 as
OLD_TCP_PORT. After looking into it a bit more, I determined that this was the port used for the web until port 80 was officially designated in January of 1992.
I recently got h2 (HTTP 2.0) running on my server.Continue reading post "HTTP 2 on Ubuntu 18.04 with Apache and PHP"
I’ve finally updated my server to Ubuntu 18.04 using
I spent numerous hours looking into what appear now to be separate gzipping issues / non-issues with my site.Continue reading post "#1724"
Not sure if it was a recent Mac security update or a change with macports, but my local apache server broke and is requiring quite a bit of work to get it functional again.
I decided to contact Dreamhost about my Apache logs showing 200 statuse codes for all
mod_rewrite responses. It took seven back-and-forths to get across what was happening, discuss options, and conclude that “DreamHost systems are configured with a default environment meant to meet the most common webapp and customer requirements”.
I’ve done some more testing on the problem I mentioned before of all requests showing up as
200‘s in the Apache log on my Dreamhost shared server. I’m pretty sure it’s specific to their