Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Oh, I meant which apache configurations... I haven't really thought through the problems we might get letting random people configure apache with htaccess. It's probably fine. What do you think?
Comments
Comment #2
mikeytown2 commentedJust a heads up that because of the non-standard apache setup, the highest score one can ever get on https://developers.google.com/speed/pagespeed/insights/ is a 99/100 or 97/100 when using this service.
Comment #3
mikeytown2 commentedIf the site is still up by the time you read this you can look at the scores here
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%...
Comment #4
greg boggsDo you have the needed configuration changes handy?
Comment #5
mikeytown2 commentedDepends on your configuration but here’s a quick start https://linode.com/docs/web-servers/apache/how-to-set-up-htaccess-on-apa...
Comment #6
greg boggsOh, I meant which apache configurations... I haven't really thought through the problems we might get letting random people configure apache with htaccess. It's probably fine. What do you think?
Comment #7
mikeytown2 commentedThis set from core
https://cgit.drupalcode.org/drupal/tree/.htaccess#n72
And this from AdvAgg
https://cgit.drupalcode.org/advagg/tree/README.txt#n239
Comment #8
mikeytown2 commentedIn terms of opening up .htaccess I think the only thing they could mess with would be their own site; so after 24 hours it’ll be gone
Comment #9
greg boggsRight... and they can already run arbitrary code as the web server.
Comment #10
mikeytown2 commentedYeah eval and your own patches means it’s open for the most part
Comment #11
mikeytown2 commentedThis will allow for core's .htaccess files to be loaded on apache start and not change unless apache restarts
https://drupal.stackexchange.com/a/108346/314
This will still not allow for advagg .htaccess but will allow core's