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
GET endpoints which accept a metadata query parameter are not parsing that parameter correctly if the metadata value contains the colon character (:).
The API specification requires the metadata query parameter to be encoded as key:value. So if the key is cklWebDbSite and the value is 0.0.0.0:8080, the query parameter is encoded as cklWebDbSite:0.0.0.0:8080.
The API implementation handles the metadata query parameter like this:
csmig
changed the title
bug: metadata predicate value with : not being parsed correctly
bug: metadata query param with : not being parsed correctly
Aug 30, 2024
GET endpoints which accept a
metadata
query parameter are not parsing that parameter correctly if the metadata value contains the colon character (:
).The API specification requires the
metadata
query parameter to be encoded askey:value
. So if the key iscklWebDbSite
and the value is0.0.0.0:8080
, the query parameter is encoded ascklWebDbSite:0.0.0.0:8080
.The API implementation handles the metadata query parameter like this:
stig-manager/api/source/service/AssetService.js
Line 210 in 2c56ce1
This will not correctly recover
value
if it contains a colon. For the example above, it returns the value only up to the colon (0.0.0.0
).Affected endpoints:
The likely fix is to change the implementation to:
The text was updated successfully, but these errors were encountered: