From jims.account at gmail.com Fri Dec 9 18:09:13 2022 From: jims.account at gmail.com (Jim Olson) Date: Fri, 9 Dec 2022 12:09:13 -0600 Subject: Hitch fails to start. Message-ID: I have been trying unsuccessfully to get hitch to run on a Debian 10 based VPS. ? hitch.service - Hitch TLS unwrapping daemon ?? Loaded: loaded (/lib/systemd/system/hitch.service; enabled; vendor preset: enabled) ?? Active: failed (Result: exit-code) since Fri 2022-12-09 12:51:44 EST; 6s ago ???? Docs: https://github.com/varnish/hitch/tree/master/docs ?????????? man:hitch(8) ? Process: 6850 ExecStart=/usr/sbin/hitch --user _hitch --group _hitch --config /etc/hitch/hitch.conf --quiet (code=exited, status=1/FAILURE) ?Main PID: 6850 (code=exited, status=1/FAILURE) Dec 09 12:51:44 racknerd-395538 systemd[1]: hitch.service: Service RestartSec=100ms expired, scheduling restart. Dec 09 12:51:44 racknerd-395538 systemd[1]: hitch.service: Scheduled restart job, restart counter is at 5. Dec 09 12:51:44 racknerd-395538 systemd[1]: Stopped Hitch TLS unwrapping daemon. Dec 09 12:51:44 racknerd-395538 systemd[1]: hitch.service: Start request repeated too quickly. Dec 09 12:51:44 racknerd-395538 systemd[1]: hitch.service: Failed with result 'exit-code'. Dec 09 12:51:44 racknerd-395538 systemd[1]: Failed to start Hitch TLS unwrapping daemon. The packages are being pulled from the repository https://packagecloud.io/varnishcache/varnish60lts/ubuntu trusty main Is there anything that can be done to get hitch working? From guillaume.quintard at gmail.com Sat Dec 10 19:04:22 2022 From: guillaume.quintard at gmail.com (Guillaume Quintard) Date: Sat, 10 Dec 2022 11:04:22 -0800 Subject: Hitch fails to start. In-Reply-To: References: Message-ID: Hi Jim, Could you share your hitch.conf, as well as the output of "systemctl cat hitch", please? -- Guillaume Quintard On Fri, Dec 9, 2022 at 10:10 AM Jim Olson wrote: > I have been trying unsuccessfully to get hitch to run on a Debian 10 > based VPS. > > ? hitch.service - Hitch TLS unwrapping daemon > Loaded: loaded (/lib/systemd/system/hitch.service; enabled; vendor > preset: enabled) > Active: failed (Result: exit-code) since Fri 2022-12-09 12:51:44 > EST; 6s ago > Docs: https://github.com/varnish/hitch/tree/master/docs > man:hitch(8) > Process: 6850 ExecStart=/usr/sbin/hitch --user _hitch --group _hitch > --config /etc/hitch/hitch.conf --quiet (code=exited, status=1/FAILURE) > Main PID: 6850 (code=exited, status=1/FAILURE) > > Dec 09 12:51:44 racknerd-395538 systemd[1]: hitch.service: Service > RestartSec=100ms expired, scheduling restart. > Dec 09 12:51:44 racknerd-395538 systemd[1]: hitch.service: Scheduled > restart job, restart counter is at 5. > Dec 09 12:51:44 racknerd-395538 systemd[1]: Stopped Hitch TLS unwrapping > daemon. > Dec 09 12:51:44 racknerd-395538 systemd[1]: hitch.service: Start request > repeated too quickly. > Dec 09 12:51:44 racknerd-395538 systemd[1]: hitch.service: Failed with > result 'exit-code'. > Dec 09 12:51:44 racknerd-395538 systemd[1]: Failed to start Hitch TLS > unwrapping daemon. > > The packages are being pulled from the repository > https://packagecloud.io/varnishcache/varnish60lts/ubuntu trusty main > > Is there anything that can be done to get hitch working? > > > > _______________________________________________ > varnish-misc mailing list > varnish-misc at varnish-cache.org > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy.lecour at gmail.com Tue Dec 13 18:57:24 2022 From: jeremy.lecour at gmail.com (=?UTF-8?B?SsOpcsOpbXkgTGVjb3Vy?=) Date: Tue, 13 Dec 2022 19:57:24 +0100 Subject: Header names case sensitivity Message-ID: Hi there, I've originally posted an issue in the GitHub repository, but was kindly reminded that it's not the place to have this kind of discussion. I'm sorry about that. https://github.com/varnishcache/varnish-cache/issues/3883 To summarize briefly, I'm wondering if we can use header names in lowercase or mixed-case in VCL (or both). I can see some VCL code (for example the output of `varnishd -x builtin`) with header names in lowercase and some in mixed-case, but I suspect that it doesn't really matter and that both cases are supported in the same way. I wish I could get a confirmation before putting all my header names in lowercases without fear of breaking something. In the GitHub issue Dridi said > VCL was historically designed when HTTP/1 was the only player in town and case sensitivity of the header names is enforced at the h2 protocol level. I'm not sure if this means that regardless of the protocol used (1.0, 1.1, or 2) at the request level the headers are already normalized in lowercase internally and mixed-case keywords are still there for backward compatibility. Thanks for your help here. -- J?r?my Lecour : https://jeremy.lecour.fr - http://twitter.com/jlecour -------------- next part -------------- An HTML attachment was scrubbed... URL: From phk at phk.freebsd.dk Tue Dec 13 21:29:09 2022 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Tue, 13 Dec 2022 21:29:09 +0000 Subject: Header names case sensitivity In-Reply-To: References: Message-ID: <202212132129.2BDLT9oc072720@critter.freebsd.dk> -------- J?r?my Lecour writes: > To summarize briefly, I'm wondering if we can use header names in lowercase > or mixed-case in VCL (or both). As far as I know, we always treat header names as case insensitive in Varnish. I think what dridi was referring to is that H2 insist they be lower-case, on the wire, but our code takes care of that. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From jeremy.lecour at gmail.com Wed Dec 14 09:52:52 2022 From: jeremy.lecour at gmail.com (=?UTF-8?B?SsOpcsOpbXkgTGVjb3Vy?=) Date: Wed, 14 Dec 2022 10:52:52 +0100 Subject: Header names case sensitivity In-Reply-To: <202212132129.2BDLT9oc072720@critter.freebsd.dk> References: <202212132129.2BDLT9oc072720@critter.freebsd.dk> Message-ID: On Tue, Dec 13, 2022 at 10:29 PM Poul-Henning Kamp wrote: > J?r?my Lecour writes: > > > To summarize briefly, I'm wondering if we can use header names in lowercase > > or mixed-case in VCL (or both). > > As far as I know, we always treat header names as case insensitive in Varnish. > > I think what dridi was referring to is that H2 insist they be lower-case, > on the wire, but our code takes care of that. Thanks for the clarification. I'll do some verification. I also wonder if changing the casing of headers produced by Varnish (X-Varnish ?) might break some implementation in the willd. -- J?r?my Lecour : https://jeremy.lecour.fr - http://twitter.com/jlecour -------------- next part -------------- An HTML attachment was scrubbed... URL: From phk at phk.freebsd.dk Wed Dec 14 09:56:45 2022 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Wed, 14 Dec 2022 09:56:45 +0000 Subject: Header names case sensitivity In-Reply-To: References: <202212132129.2BDLT9oc072720@critter.freebsd.dk> Message-ID: <202212140956.2BE9ujq5075959@critter.freebsd.dk> -------- J?r?my Lecour writes: > I also wonder if changing the casing of headers produced by Varnish > (X-Varnish ...) might break some implementation in the willd. It should not, but yeah, not everybody reads RFCs recreationally... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From jeremy.lecour at gmail.com Wed Dec 14 10:03:23 2022 From: jeremy.lecour at gmail.com (=?UTF-8?B?SsOpcsOpbXkgTGVjb3Vy?=) Date: Wed, 14 Dec 2022 11:03:23 +0100 Subject: Header names case sensitivity In-Reply-To: <202212140956.2BE9ujq5075959@critter.freebsd.dk> References: <202212132129.2BDLT9oc072720@critter.freebsd.dk> <202212140956.2BE9ujq5075959@critter.freebsd.dk> Message-ID: On Wed, Dec 14, 2022 at 10:56 AM Poul-Henning Kamp wrote: > not everybody reads RFCs recreationally... What ?? I'm shocked ! :D I spent 2 hours last night reading parts of the RFC9110 about HTTP and I've learnt a lot about HTTP headers. For example, the "X-" prefix for non-standard headers has been deprecated since 2012. It was a good idea in theory but proven to be counter productive, based on the long running experimentation in email and SIP (and HTTP). For Varnish I guess we're stuck with the X- prefix since it became a de-facto standard. -- J?r?my Lecour : https://jeremy.lecour.fr - http://twitter.com/jlecour -------------- next part -------------- An HTML attachment was scrubbed... URL: From dridi at varni.sh Thu Dec 15 16:25:40 2022 From: dridi at varni.sh (Dridi Boukelmoune) Date: Thu, 15 Dec 2022 16:25:40 +0000 Subject: Header names case sensitivity In-Reply-To: References: <202212132129.2BDLT9oc072720@critter.freebsd.dk> <202212140956.2BE9ujq5075959@critter.freebsd.dk> Message-ID: On Wed, Dec 14, 2022 at 10:05 AM J?r?my Lecour wrote: > > On Wed, Dec 14, 2022 at 10:56 AM Poul-Henning Kamp wrote: > > not everybody reads RFCs recreationally... > > What ?? I'm shocked ! :D > > I spent 2 hours last night reading parts of the RFC9110 about HTTP and I've learnt a lot about HTTP headers. > > For example, the "X-" prefix for non-standard headers has been deprecated since 2012. > It was a good idea in theory but proven to be counter productive, based on the long running experimentation in email and SIP (and HTTP). > > For Varnish I guess we're stuck with the X- prefix since it became a de-facto standard. We can always rename X-Varnish to something else but we'd need a good reason to break existing setups. On the other hand you have the ability to rename the header in VCL and have access to the req.xid and bereq.xid variables to build your own transaction tracking header. Cheers From guillaume.quintard at gmail.com Tue Dec 20 17:32:04 2022 From: guillaume.quintard at gmail.com (Guillaume Quintard) Date: Tue, 20 Dec 2022 09:32:04 -0800 Subject: any VEXT examples? Message-ID: Hi all! I saw the 7.2 change notes mentioning Varnish Extensions, which sound pretty interesting for a couple of projects I had in mind and which wouldn't totally fit as vmods, so I'd love to take a stab at it. I looked at the source and couldn't find any examples or meaningful documentation, would you have any pointers on that front! Happy holidays! -- Guillaume Quintard -------------- next part -------------- An HTML attachment was scrubbed... URL: From phk at phk.freebsd.dk Tue Dec 20 19:57:46 2022 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Tue, 20 Dec 2022 19:57:46 +0000 Subject: any VEXT examples? In-Reply-To: References: Message-ID: <202212201957.2BKJvkeM062620@critter.freebsd.dk> -------- Guillaume Quintard writes: > I saw the 7.2 change notes mentioning Varnish Extensions, which sound > pretty interesting for a couple of projects I had in mind and which > wouldn't totally fit as vmods, so I'd love to take a stab at it. > > I looked at the source and couldn't find any examples or meaningful > documentation, would you have any pointers on that front! There isn't much except for the basic mechanism yet, because, as is often the case, once we get to the details, it's not /that/ obvious how things should work :-) Input is therefore most welcome. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From guillaume.quintard at gmail.com Mon Dec 26 21:34:05 2022 From: guillaume.quintard at gmail.com (Guillaume Quintard) Date: Mon, 26 Dec 2022 13:34:05 -0800 Subject: introducing vmod_fileserver Message-ID: Happy holidays to you all! I had a few days off, so of course I decided to finally get some hacking time on Varnish, and decided to once again spend some time on rust and backends. Here's what I got: https://github.com/gquintard/vmod_fileserver As the name suggests, this vmod allows you to serve files directly from disk, without relying on an external backend. That can be useful for a bunch of things like returning a healthcheck file generated by another process, providing an error page in case of backend failure, or just to provide some test data quickly. Essentially, this vmod: - allows you to set a root directory and serve files from there - supports HEAD/GET - supports conditional requests with if-none-match and if-modified-since The API is minimal, and the code hasn't seen any production traffic yet, so be careful! But if you can test it and there are some use cases not covered here, I'll happily hear your feedback. Also, if you are a C developer curious about rust, you might want to look at the code: https://github.com/gquintard/vmod_fileserver/blob/main/src/lib.rs I commented it as much as I could, and because varnish-rs is far from complete, you'll see a lot of C idiosyncrasies that aren't "hidden" by rust, and therefore the code might look more familiar. Anyway, that's all for me, let me know what you think! -- Guillaume Quintard -------------- next part -------------- An HTML attachment was scrubbed... URL: