[Seaside-dev] HEAD HTTP method handling in RESTful handlers/filters

[Max Leske]

Hi Esteban,

I don't see why it shouldn't be possible to handle HEAD requests explicitly. I think it's a good idea to have the option (even though most people won't need and shouldn't use it).

Cheers,
Max


On 2 Aug 2021, at 21:33, Esteban Maringolo wrote:

> Hi,
>
> As per the RFC the HEAD is identical to a GET but without the body,
> but given you might want to have full control of all requests coming
> to your REST handler, it might be the case you want to answer HEAD
> methods differently (e.g. to avoid serializing things and/or reading
> them from the DB).
>
> For some reason the HEAD HTTP method is not available as method in
> WARouteBuilder, so it is not possible to have a specific HEAD handling
> for a certain route.
>
> Does it make sense not having HEAD support as a possible method for a route?
> Having HEAD returning different headers to that of a common GET would
> make it not compliant?
>
> This might require not only implementing the configuration pragma in
> the WARouteBuilder, but also modifying the WAServerAdaptor to forward
> native HEAD requests to the handlers.
>
> Regards!
>
> Esteban A. Maringolo
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20210802/c7bd87b4/attachment.sig>