#nginx 1.28.0 has been released (#http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13) https://nginx.org/
#nginx 1.28.0 has been released (#http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13) https://nginx.org/
#Freenginx 1.28.0 has been released (#nginx / #http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13) https://freenginx.org/
#Freenginx 1.27.6 has been released (#nginx / #http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13) https://freenginx.org/
#nginx 1.27.5 (dev) has been released (#http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13) https://nginx.org/
Right. That's done.
The existence of an OLDPROTO environment variable opts in to the old #publicfile behaviour. This will be in the next #djbwares release. The hardest part was writing the explanation in the #httpd manual page.
Hmmm. Where was that #publicfile to-do item?
Ah, yes. It was #httpd . Hmmm.
Not sure if I asked this before: Does anyone use anything in particular to inject #apache logs into #SQL databases? I have been looking around and asking around and the only solid I got was "do not expect an apache module for that; it would introduce too much latency to each request" in #httpd@libera.chat.
a2enmod expires cache cache_disk
<LocationMatch "^/social/[^/]+/[xys]/|^/social/nodeinfo_2_0">This will use the disk cache to cache everything under the $username/s/, /x/ and /y/ paths, as well as for the
CacheEnable disk
Header set Cache-Control "max-age=86400, public" "expr=%{REQUEST_STATUS} == 200"
ExpiresActive On
ExpiresDefault "access plus 86400 seconds"
</LocationMatch>
/nodeinfo_2_0
path, utilizing mod_expires
to generate the appropriate cache headers (for lazy ones like me). In this case caching it for 1 day.no-cache
on that location and mod_expires
will honor that if we don't override it. I set it to the same Cache-Control value as mod_expires
would. (I use mod_expires
because it will additionally calculate the date and put that in the expires
header. (hence the name I guess a2enmod expires cache cache_disk
CacheRoot /var/cache/apache2/mod_cache_diskThis will use the disk cache to cache everything under the /s/ Path, same as the original ngnix tutorial, Utilizing the mod_expires to generate the appropriate cache headers (for lazy ones like me), In this case caching it for 30 days.
CacheQuickHandler off
CacheMaxFileSize 10000000
CacheLock on
##Optional while testing stuff;
CacheDetailHeader on
##My Instance is under "/social"; so this needs to be adapted:
<LocationMatch "^/social/[^/]+/s">
CacheEnable disk
ExpiresActive On
ExpiresDefault "access plus 30 days"
</LocationMatch>
If I would like to use relayd to add security headers and tls to my website hosted via httpd, is there any solution how to specify custom path to keypair to tls?
Scheduling HTTP Streams
by Alexander Krizhanovsky.
Understand how a web server manages millions of concurrent web requests.
* Differences in treatment for progressive JPEG vs a PNG.
* Resilient against DDoS attacks and other vulnerabilities.
* Compare Nginx, Envoy, Apache.
https://fosdem.org/2025/schedule/event/fosdem-2025-4903-scheduling-http-streams/
Live stream:
https://live.fosdem.org/watch/ua2220
New blog post - Rewriting URL's using OpenBSD and httpd.conf
This is just a reminder for future me, when I forget how I got it to work next time.
There's nothing particularly interesting, unless you also get stuck trying to get a URL redirected to another directory.
https://martin.hatstand.org.uk/posts/2024/rewriting-with-httpd/
Since I made the #httpd specific guide for #openbsd via https://httpd.rocks, I thought it would only be fair to make a guide for those who prefer #caddy on #linux
It's not live yet, but hopefully I'll get things finished up by the end of the week :)
Updated https://httpd.rocks/
- Added a simple TOC
- Minor styling changes to break content apart more cleanly
- WWW to non-WWW forwarding is now handled via httpd (instead of haproxy)
That is all
#nginx 1.27.3 (dev) has been released (#http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13) https://nginx.org/
Is it good idea to host my website with #OpenBSD #httpd without domain name, just ip address? I do not need domain because of better remembering, but there are maybe other reasons why to use domain... I suppose there should be a problem with tls and maybe https, I'd like to use https but when site is just static https may not be required.