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
{{ message }}
Repository navigation
Commit cd16012
Browse filesBrowse the repository at this point in the historyBrowse files
fix(agiloft): redact encoded credentials and separate declines from unconfirmed writes
Review round 2.
Redaction only replaced the raw credential strings, but the values are sent
form-encoded, so an error page quoting the submitted parameters quotes the
encoded spelling. A password with a space leaves as a%20b or a+b and sailed
past a replace that only knew a b. All three spellings are now replaced,
longest first.
Redaction also ran after truncation on the create path, so clipping the text
could cut through a credential and leave a prefix that no longer matched
anything being replaced. The order is reversed and the reason recorded, since
the two read as interchangeable and are not.
The non-OK create branch always warned that the record might exist, including
on a 4xx validation decline where Agiloft had refused the request and written
nothing. That is the opposite of the rule this branch introduces: it told the
caller not to retry a create that never happened. A 4xx carrying a typed
exception is now reported as a definite refusal; a 5xx keeps the warning,
because a server fault may have committed first.
Redirects were refused on the calls carrying credentials in a body but not on
executeAgiloftRequest's operation fetch or on logout, both of which send a
Bearer token that secureFetchWithPinnedIP would replay to a redirect host.
Those are the calls behind list tables and saved search.
0 commit comments