LiteSpeed statt Nginx/Apache

Die meisten WordPress-Websites werden mit Nginx, Apache oder eine Kombination aus beiden angetrieben. Jede Lösung hat ihre eigenen Vor- und Nachteile. Der größte Vorteil von Apache ist die Flexibilität: Durch spezielle Dateien im Webverzeichnis - du hast sicher schon von den .htaccess-Dateien gehört - können f…

https://www.leo-skull.de/litespeed-statt-nginx-apache/

#LeoSkullIntern #Technik #Apache #LiteSpeedWebServer #Nginx #OpenLiteSpeed #Performance

...und damits hier nicht ganz so leer aussieht, direkt mal eine Umfrage. Gern teilen.

#web #webserver #linux #nginx #apache #openlitespeed #seo #webdesign #agency #agentur #wordpress #poll

Auf welchen Webserver setzt ihr?

@The_KamikaZEN have you contacted #DreamHost support at all. Do they support a `.htaccess` file in the `.well-known` directory? What web server software are they using? #Nginx #Apache #LiteSpeed #OpenLiteSpeed If they have have any special server rules/restrictions setup for that path that might be the problem. This is unfortunately one of the reasons why getting the #ActivityPub plugin working on all #WordPress sites is such a challenge. This needs hosting provider support.

@letsencrypt

@tomfinley@wptoots.social actually, you are having the #Cloudflare issue on your #WordPress site with #ActivityPub . I just visited your site via my web browser and I am getting JSON when I should be getting HTML.

I was having this same problem with my #OpenLiteSpeed caching which I then managed to setup my OLS caching to be able to create a cached version based on the Accept header.

@jasontucker @alexstandiford @tomfinley@tomfinley.co

@ramsey question about PHP release announcements. I'm noticing that #PHP 8.0 hasn't been getting release announcements only PHP 8.1 & 8.2. Is there a reason for this? I ask because I'm maintaining a #Docker image for #OpenLiteSpeed that includes PHP. I'm trying to stay on top of keeping it up-to-date and so have setup notifications for myself by monitoring the PHP release announcements. Thanks!

https://news-web.php.net/php.announce

@webaware to be very clear this is not a solution for the #OpenLiteSpeed server caching. Using Rewrite rules to solve this follows exactly what they recommend on configuration. Additionally, there can be issues with the Accept header causing way too many duplicate copies of the same thing, because there can be Accept headers that are slightly different.

@chrisshaw @timnolte @jasontucker @dustinrue

@chrisshaw @timnolte so I just cleared the #OpenLiteSpeed cache for my author page so it is at least loading as HTML for normal web users.

As for #Cloudflare there are some known issues with that also and using the #ActivityPub plugin. @jasontucker @dustinrue have both worked with that setup. I am currently moving all of my DNS to Cloudflare but sort of prefer to leverage the OpenLiteSpeed web server caching. Looks like I still have some work to do in that regard.

@chrisshaw @timnolte oh, so interesting, I am seeing that for some reason my #OpenLiteSpeed caching is still not handling my author page correctly. It cached my author page as #JSON instead of #HTML. Blah, this is one of the major issues with the #WordPress #ActivityPub plugin is proper cache handling.

@glecharles @jasontucker my site is working @timnolte which is the same as this https://www.timnolte.com/author/timnolte/ but, crap...I thought my caching fix for #OpenLiteSpeed was working but I'm seeing #JSON instead of #HTML in my browser. 🤦

@webaware @pfefferle Even the Fastly article I shared indicates that a simple rule that uses an explicit value for the the "Accept" header would create too many different and unnecessary cached versions. So in the case of the #OpenLiteSpeed server the "Vary: Accept" header is actually useless because it doesn't support creating different cached versions based on it. And it also doesn't help when the request doesn't have it either.

2/2

@webaware @pfefferle I will have to do some testing to confirm whether #OpenLiteSpeed honors the "Accept: Vary" header.

@webaware so I'm not clear on what you are suggesting. Updating any plugin with that headser isn't going to control how the #OpenLiteSpeed cache is created. The OLS web server documentation indicates that you need to use the "Cache-Control: vary=" Rewrite to create separate caches, like when you have a multilingual site for example. Also, as @pfefferle points out that "Vary: Accept" headset would actually have to come #Mastodon or other #ActivityPub sources.

So the solution for #OpenLiteSpeed caching is to use this in order to have 2 different caches for the same endpoint.

#BEGIN ActivityPub Cache Handling
<IfModule LiteSpeed>
RewriteEngine On
CacheLookup on
RewriteCond %{HTTP_ACCEPT} ^application\/activity\+json$
RewriteRule .* – [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+activitypub]
</IfModule>
#END ActivityPub Cache Handling

2/2

OK, so I'm not sure about a broader solution. However, I have finally figured out how to properly cache HTML & Activity+JSON requests with #OpenLiteSpeed & the #ActivityPub plugin for #WordPress. It is possible that this might be usable for an #Apache setup using my original redirect method.

1/2

OK, so for people using the #ActivityPub #WordPress plugin from @pfefferle and are using caching that causes problems with return #JSON to web visitor, instead of #HTML, or HTML to ActivityPub requests instead of JSON, I think I have a working solution. I have just finally got around to testing my theory on my #OpenLiteSpeed server by leveraging a Rewrite Rule. I haven't fully confirmed if the requests are being cached.

1/2

So what are #FOSS projects doing to serve up #Docker images? I just got a stupid email from Docker that states that I now have to pay them to host my free #OpenLiteSpeed image for #arm64 that I've spent months on tuning and supporting. I'm really starting to hate Docker. 💩

@imrehg yeah, so this is a widespread problem with just about all caching, especially for WordPress sites. @jasontucker had some major problems when using #Cloudflare in front of his #WordPress site. I have odd issues as well with #OpenLiteSpeed caching in front of my site.

@andyfragen @ru I think the thing for me that is a hard sell is that SpinupWP is just a layer on top of a cloud hosting providers, like #DigitalOcean. I can already spin up a 1-click #CyberPanel with #OpenLiteSpeed droplet with little effort and cut out the extra cost, this would be at the Personal level. For my personal stuff I just can't justify spending $40/mo on top of VPS costs of $15+/mo for full support/management.

@alexstandiford I'm currently in the process of migrating my current #DigitalOcean droplet setup over to a container-based setup on the #OracleCloud Infrastructure free tier, all running on #arm64. Sort of got into the weeds as I ended up building my own #OpenLiteSpeed #Docker image that can run on arm64. I'm on the fence on whether I really like the setup or not. It's not 1-click simple, so I may look at figuring out a solution to that. It seems with #containers nothing is every 1-click.

@jasontucker @tomfinley so on the IndieWeb Slack @pfefferle mentioned:

"There is already a possibility to show the json by adding „/activitypub“ behind every author, post or page URL. For example https://notiz.blog/2022/11/14/the-at-protocol/activitypub/ Maybe you can redirect to this page!"

I'm going to try to setup a rewrite rule on my #OpenLiteSpeed server and see if that makes a difference or not. I'm not sure that it is even something that can be done with Cloudflare though.