wiretap fails to authenticate a operation that uses the same route but unique via a fragment about wiretap HOT 4 CLOSED

As mentioned in #96

After attempting to solve this, I was confused as to why the correct path could not be found.

The http.Request.URL.Fragment was always missing when making a curl request or via postman etc. I was unable to perform any kind of lookup when a fragment was used, because any request made to wiretap using a fragment was just missing the fragment each time.

So then I looked a little deeper. I found this:

golang/go#3805

Fragments are never sent in HTTP.  They're purely a local browser concept.

There is no way for me determine which path is being requested when the OpenAPI specification uses a fragment as a delimiter. The fragment is never picked up by the standard library.

Which pulls into question the legitimacy of using fragments at all in OpenAPI specs. They are quite useless it seems and should not be used as delimiters for paths.

Marking this as a wontfix, because there is nothing I can do to make it work.

from wiretap.

@daveshanley a strategy we are seeing people using to deal with this is it effectively becomes a join of the two operations, on their servers the two routes or directed to the same handler but they are determining the operation based on the inputs, so it is effectively a oneOf between the request bodies/response bodies etc.

Totally understand if you want to keep this as wontfix, we can find some other way to deal with this but it is theoretically possible

from wiretap.

I think this strategy is a little bit odd to be honest, it means parsing the body to determine the schema, in order to figure out which fragment to use - which to me feels like a considerable hack. It feels like it's going against the spirit of the standard, in order to make it work.

from wiretap.

So technically yes it does look like the OpenAPI initiative has decided to not make this official OAI/OpenAPI-Specification#1635 but in the wild it is getting used to differentiate APIs that share a path but can accept different request bodies, we have come across a few cases of this and various tooling does seem to support it (including ours)

from wiretap.