GWGTrying to figure out. Are HEAD requests for webmention verification a good or bad thing? They are mentioned in the spec. But there are suggestions that they are seen as security indicators by some sites
ZegnatHEAD responses should be the same as GET, just without the body. So it can be a performance boost doing a HEAD first and see if you actually want the body at all.
ZegnatI can see why Granary wouldn’t support them though. HEAD requests should also contain the content-length etc (as it should have all headers that GET results in), generating those are a lot of work for Granary.
ZegnatIf granary is serving a 405 to the HEAD, with an Allow header containing GET, it is doing the correct thing. And the way to respond to that is by repeating the request as a GET
ZegnatYou could even fallback to a GET request where you drop the connection once you have received the full HTTP header, to emulate a HEAD. (Though obviously do not do that if you want to do a normal GET right after.)
ZegnatDepends on your usecase GWG. I only use HEAD for things like endpoint discovery, because in those cases my entire query can actually be answered by just the HTTP headers. It makes sense then, IMO
ZegnatFor feed fetching, it is often much more to implement caching correctly on both sides. That way you get the same result, because a server may answer with a 304 (not modified) and does not have to send a body either (like with HEAD)
ZegnatHEAD doesn’t do much with bad actors either, seeing how you need the server to return the correct response. It only tangentally gives you protections against bad actors using servers they do not control
snarfedto be clear, granary is 405ing HEADs for scalability, not security. it does a lot of work before it even knows the HTTP response code, and i'm choosing not to burn that work right now on very low quality requests
[frank]I could use some ideas and pointers for a good service. I use Inoreader as my feedreader (still for now) and it can trigger webhooks when I star an article. I am looking for a good service to receive webhooks to and let me send out a micropub request to my server. I tried Zapier but it's quite complicated....
[frank]Looks like it's working, but Inoreader has a weird way of formatting the incoming payload. I might need a multi-step zap which will cost me money...meh...
Zegnat!tell jeremycherfas scratch that, I just took an extra minute and noticed the mf2 parser is seeing an runtimeexception. So it is that ephemeral thing you talked about at IWC.
[jeremycherfas]Yup. Thanks Zegnat. That might be the same issue I had a week or so ago, which I thought I had debugged. I’m going to have to save this until I am back at my desk on Thursday.
Loqi[jeremycherfas]: Zegnat left you a message 19 minutes ago: The W3C validator talks about some wrongly closed HTML elements on jeremycherfas.net, that may be why mf2 parsers have a hard time reading the page (no h-card: https://php.microformats.io/?url=https%3A%2F%2Fwww.jeremycherfas.net%2F). Maybe worth debugging?
Loqi[jeremycherfas]: Zegnat left you a message 18 minutes ago: scratch that, I just took an extra minute and noticed the mf2 parser is seeing an runtimeexception. So it is that ephemeral thing you talked about at IWC.
ZegnatThe most recent release has updated twig, but don’t see anything special otherwise. Though it might be in a commit with a less than descriptive commit message
[manton], jackjami_, [jeremycherfas] and kisik21 joined the channel