"uri" defined in HTTPMatchRequest&HTTPRedirect is path rather than uri

[idouba]

A standard uri should look like this: URI = scheme:[//authority]path[?query][#fragment].
And the uri referenced in VirtualService, such as HTTPMatchRequest, HTTPRedirect is simply a path. The field uri seems be a little confusing, maybe path can be better understood.

[esnible]

@geeknoid This Issue seems to better addressed in the https://github.com/istio/api repository.

[rshriram]

@frankbu what do you think of this? I too think that the path is a better term for uri.

[frankbu]

Do I think path would be a better field name than uri? Maybe.

Do I think it's worth deprecating the old field and creating a new one? Probably not.
We would also need to change the ignoreUriCase field to ignorePathCase to be consistent.

I think maybe we should instead update the documentation to clearly say that it's the path part of the uri that the field is matching.

[howardjohn]

While I think this is technically correct, the cost to fix it outweighs the benefit so I think we are stuck with the current state. Note Gateway API HTTPRoute did not make the same mistake