Chewing_Bever/lander

Support HEAD Requests #14

New issue

Closed

opened 2023-10-28 10:54:08 +02:00 by Jef Roosens · 1 comment

Jef Roosens commented

2023-10-28 10:54:08 +02:00

Owner

Currently we don't support HEAD requests at all (we return 501). This could be useful to implement, as I also often use this feature in other tools.

Currently we don't support HEAD requests at all (we return 501). This could be useful to implement, as I also often use this feature in other tools.

Jef Roosens commented

2023-11-16 15:15:03 +01:00

Author

Owner

We might be able to transparently support HEAD requests for GET requests by only running the request steps if it's a HEAD request, and only writing the headers then. This would require the application to determine all of the required response data in the request state, but for Lander, this is already the case anyways. A good idea for this would perhaps be to hide writing of headers from the response routes.

We might be able to transparently support HEAD requests for GET requests by only running the request steps if it's a HEAD request, and only writing the headers then. This would require the application to determine all of the required response data in the request state, but for Lander, this is already the case anyways. A good idea for this would perhaps be to hide writing of headers from the response routes.

Jef Roosens added the

label 2023-11-16 18:07:53 +01:00

Jef Roosens closed this issue

2023-12-07 13:43:28 +01:00

Sign in to join this conversation.

No labels

Kind/Enhancement

Project/Landerctl

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Chewing_Bever/lander#14

No description provided.