Mike Amundsen

I know this thread is getting quite long; good stuff here. I wanted to add one more thing to the mix when considering how to go about documenting a "Hypermedia...

the HAL-FORMS specification (here: https://rwcbook.github.io/hal-forms/) accounts for the ability to send body-less unsafe requests (see: https://rwcbook.github.io/hal-forms/#_code_properties_code). FWIW, the HAL-FORMS example you show doesn't comply w/ the linked spec since the...

no problem. there are a couple "flavors" of HAL-FORMS out there, so i was just ticking a box there. the real convo is about the body-less POST. the spec was...

I suspect it's a rule in prism that blindly attempts to parse a JSON object body when the `content-type: application/json` header is passed during _some_ HTTP methods (e.g. POST/PUT/PATCH) --...

my view on this is that the Prism server has a bug. would be interested in how other frameworks handle the same use case. FWIW, the HAL-FORMS spec uses *SHOULD*,...

@evert : > I think it's pretty good to expect for a tool to attempt to parse the body if there was a Content-Type: application/json agreed. but it might not...

@sazzer good point.

there are not unique headers defined by this spec. also, HAL-FORMS is not designed to require authorization, etc. however, section 6.2 _refers_ to `contentType` but does not explicitly mention the...

@benhamill: I think a "tool-able" range implementation for UBER would look like this: ``` xml 1 100 ``` BTW - I'm OK w/ exploring these constraints now even if all...

pretty sure this is going to morph into another "magic string" enumeration[1]. right? [1] https://github.com/mamund/media-types/issues/24 ​