Range-Patch URI fragments aren't sent to server

[toomim]

The Range-Patch spec says this:

2.3.  URI Fragment Identifiers

   For media types which support range patches, ranges can be used as
   URI fragment identifies as well.  For example, URI:

      /api/document/1#json=/foo/bar/0

   identifies a fragment with the following content:

      {"some": "thing"}

   Multiple ranges are supported as well and they identify multiple
   fragments:

      /api/document/1#json=/foo/bar/0,/foo/bar/1

This doesn't work because anything starting with a # in a URI isn't sent to the server.

• https://en.wikipedia.org/wiki/URI_fragment
• https://stackoverflow.com/questions/14462218/is-the-url-fragment-identifier-sent-to-the-server

[mitar]

Please see https://tools.ietf.org/html/rfc5147 and https://tools.ietf.org/html/rfc7111 to understand what this section is about. It does not matter it is not send to the server. :-)

[toomim]

I see! Thank you. I totally misunderstood what these were for. This might clear up some confusion on other things as well.