#Zegnatmarks up indiewebsearchengineproofofconcept output as h-feed so it can be subscribed to
#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
#Loqi[dshanske] #166 Consider supporting head requests
#GWGSo I wanted to reexamine why I am doing things
#GWGI do HEAD requests to check for valid URLs on feed parsing as well
#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.
#ZegnatE.g. to scan it for MIME types so you know if the body is something you can parse.
#doubleloopZegnat++ on indiewebsearchengineproofofconcept h-feeds
#LoqiZegnat has 49 karma in this channel over the last year (156 in all channels)
#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.
#ZegnatAnd it is too bad to do all that work and not even serve the final body.
#doubleloopI think it needs a project codename though
#sknebel405 does mean "I won't answer that request"
#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
#ZegnatThat should probably be the default handling of everyone that does HEAD requests.
#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.)
#GWGI am just wondering if I should give up the HEAD entirely
eli_oat, eli_oat1 and [kevinmarks786] joined the channel
#[kevinmarks786]Responding to HEAD on appengine is extra work
eli_oat1, [jeremycherfas], ichoquo0Aigh9ie, GWG_, Kaja_, Anchakor_, treora_, stevestreza, callMeBaby, raucao, jackjamieson, blueyed and snarfed joined the channel
#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)
#ZegnatSo just GET with the correct cache settings, and if you get 304 you know nothing changed. No need for HEADs.
[eddie], [grantcodes] and [Rose] joined the channel
#sknebelWhereas for webmentions caching likely isn't very effective
#sknebelBut without bad actors, HEAD also doesn't do much
gRegorLove_, [grantcodes], jjuran and snarfed joined the channel
#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
#snarfed(almost all real user requests right now are GETs, not HEADs)
snarfed, [tonz], jackjamieson, leg, [tantek], snarfed1, [Rose] and [frank] joined the channel
#[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]It might be as simple as send out a curl command when a webhook is received
#snarfed[frank]: zapier and ifttt really are worth trying first
#[Rose]Yes, webhook as an action, like the images just shared. (Love the upload to Media Endpoint shortcut)
[schmarty] joined the channel
#[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...
#[frank]But then I realised I was once invited to test the new Inoreader/Zapier integration. And shazam....An even better integration
#gRegorLoveHm, the Go parser finds the h-card. More forgiving HTML parsing I guess.
#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.
#ZegnatThere is something weird going on with his site that means certain requests result in runtime errors. I just forgot because I am a little mushy.
#gRegorLoveThe runtimeexception seems to be about a missing Twig template
#Zegnatyes, but it is weird how that only happens in very rare cases
#ZegnatGET still works without the UA. Guess I’d have to run php-mf2 locally and grab full curl logs or something. If it even happens when ran locally.
#[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.
#gRegorLoveMy local copy doesn't include the UA header, just Accept
#[jeremycherfas]The run time exception is apparently fixed in a recent Grav commit. Again, cannot easily get to it before Thursday.
#ZegnatI removed the UA from curl, did not make a difference for me locally, gRegorLove
#Zegnatthat might just tell us why it is doing what it is doing
#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