Create implied GET method in some circumstances #22

New issue

Open

opened 2026-07-04 08:14:17 +02:00 by c.fahner · 0 comments

c.fahner commented

2026-07-04 08:14:17 +02:00

Owner

Currently, resource are always required to explicitly declare a GET method to avoid a ResourceException. This is due to the fact that, according to the spec, the GET method must always be available (and may never return a 405). However, in practice some resources only implement the POST method and are then required to add a dummy GET method that simply returns 404.

The framework might as well create an implied GET method (that returns 404) whenever methods other than GET, HEAD or OPTIONS have been declared.

Currently, resource are always required to explicitly declare a GET method to avoid a `ResourceException`. This is due to the fact that, according to the spec, the GET method must always be available (and may never return a 405). However, in practice some resources only implement the POST method and are then required to add a dummy GET method that simply returns 404. The framework might as well create an implied GET method (that returns 404) whenever methods other than GET, HEAD or OPTIONS have been declared.

c.fahner added the

Kind/Enhancement

label

2026-07-04 08:14:17 +02:00

c.fahner added this to the v0.2 milestone

2026-07-04 08:14:23 +02:00

c.fahner modified the milestone from v0.2 to v0.1

2026-07-04 08:14:27 +02:00

c.fahner changed title from ~~Resources should create an implied GET method when other methods exist~~ to Create implied GET method in some circumstances

2026-07-04 08:15:56 +02:00