You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
http.url MUST NOT contain credentials passed via URL in form of https://username:password@www.example.com/. In such case the attribute's value should be https://www.example.com/.
I understand this is coming from spec but for enduser it won't be evident that URL was containing username and password when it got here. Instead if we have redacted version like https://***:***@www.example.com/ it will be more evident in expressing URL contains username and password but they are redacted for security reasons.
If we don't go with redacted version it might cause ambiguity for someone checking if url contains creds or not because in span with creds and without creds will be same.
If we don't go with redacted version it might cause ambiguity for someone checking if url contains creds or not because in span with creds and without creds will be same.
Yes, I think this could be a valid concern. However, it seems the specification suggests to drop everything (see the quoted excerpt in the issue description, also see the discussion). Maybe in such cases this could be alleviated in other way, perhaps adding an attribute, if desired?
As is stated in the recent specification change :
This should be reflected in
HTTPClientAttributesFromHTTPRequest
The text was updated successfully, but these errors were encountered: