Timeline for Rest application header based vs path based service routing
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 30, 2019 at 9:32 | comment | added | Cormac Mulhall | That is quite different to using the header to construct the URI though, particularly when the construction in the header itself is resource specific (ie only done for certain types of resources) | |
| Dec 28, 2019 at 15:18 | comment | added | Laiv | Note that in HTTP, some headers are used to communicate redirection and forwarding. It's not totally out of place what the OP is asking. It's just a little bit forced because it implies something else. A router, not a mere http server. | |
| Dec 19, 2019 at 13:04 | vote | accept | Alexander Petrov | ||
| Dec 17, 2019 at 16:53 | comment | added | Cormac Mulhall | Just because you can do something doesn't mean you should. The HTTP header is concerned with facilitating the state transfer of the resource, it doesn't and shouldn't care about specific business logic of the resource (ie the different states of the specific resource). | |
| Dec 13, 2019 at 22:00 | comment | added | JimmyJames | "Don't put them in the header. This information has nothing to do with the HTTP transport level." this is a non-sequitur. | |
| Dec 12, 2019 at 19:05 | comment | added | Alexander Petrov | I think you are right. | |
| Dec 12, 2019 at 17:09 | history | answered | Cormac Mulhall | CC BY-SA 4.0 |