Why do we, by default, only care about those Resource Attributes:
And ignore:
Most probably, we assume that there must be a specific authorization to the path we are protecting with kube-rbac-proxy. Speak, is the: User allowed to Verb at Path.
But worth to investigate the behavior of the SAR request created in such a situation, if not trimmed and compare the results.
NotesRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4