On Thu, Feb 26, 2026 at 08:42:27AM +0000, Stuart Henderson wrote:
> On 2026/02/26 08:17, Rafael Sadowski wrote:
> > Joel Carnat notice that GoToSocial does not like it when we sent no
> > User-Agent and returns an HTTP/418. This simple diff adds User-Agent to
> > all HTTP/HTTPS checks.
> > 
> > As I see it, we use "User Agents" in other places (ftp,acme-client...).
> > When I look at all my (aws) load balancers and checks, I get a user
> > agent from all of them.
> 
> ok sthen for the parse.y change, but I don't like the manual change
> (would you expect to see similar in docs for rpki-client, acme-client,
> etc?)

I agree, the user-agent is just a detail that does not need to be
documented.

OK claudio on the parse.y change as well.
 
> >  header to query a specific hostname at the target host.
> > +A
> > +.Dq User-Agent: relayd
> > +header is always included in the request.
> >  To validate the HTTP return code, use this shell command:
> >  .Bd -literal -offset indent
> >  $ echo -n "HEAD <path> HTTP/1.0\er\en\er\en" | \e
> 

-- 
:wq Claudio