Rahul Gupta
Rahul Gupta
*[[Introduction copied from the Draft](http://cxres.github.io/per-resource-events/protocol/#introduction)]* Per Resource Events is a minimal protocol built on top of HTTP that allows clients to receive notifications directly from a resource of interest. Unlike...
I was recently trying to figure out how to store arbitrary data in a Solid-Pod (see my comments on Gitter over the past month on the specification channel) such that...
As discussed in solid/notifications#187 [RFC9205](https://httpwg.org/specs/rfc9205.html#specifying-the-use-of-http) recommends: > Specifications should use [[HTTP]](https://httpwg.org/specs/rfc9205.html#HTTP) as the primary reference for HTTP; it is not necessary to reference all of the specifications in the HTTP...
Write rules for Auxiliary Resources fail to account for many scenarios: Spec says: > When a PUT or PATCH method request targets an auxiliary resource, the server MUST create or...
Since I have already started to irk folks on the current sfbis-05 draft, I thought I might as well take the opportunity to do a proper job of it. I...
I was playing around with structured headers (pretty much coinciding with Tommy's last, last-call), which prompted me to look into the spec. It is unclear to me if what happens...
The header fields must be registered in the Hypertext Transfer Protocol (HTTP) Field Name Registry and not the "Message Headers" registry as was the case in days of yore. See...
HTTP/2 uses a completely different syntax to describe requests/responses. It is not as simple as replacing `HTTP/1.1` with `HTTP/2` and adding support for pseudo-headers (which is what I see as...
Are the list of PI's used by xml2rfc documented? Alternatively, is it possible to get a list by looking at the code.
By convention markdown syntax inside block elements is not processed. And remark respects those conventions (see rehypejs/rehype-raw#8). A number of items such as `` inside blockquotes, epigraphs etc. do not...