CCM-20515: switched client-provided URI placeholders to use curly brackets#1087
CCM-20515: switched client-provided URI placeholders to use curly brackets#1087cgitim wants to merge 6 commits into
Conversation
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-20515 |
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-20515 |
| ("personalisation", None), | ||
| ("/<client-provided-message-status-URI>", None), | ||
| ("/<client-provided-channel-status-URI>", None), | ||
| ("/{client-provided-message-status-URI}", None), |
There was a problem hiding this comment.
At of curiosity, why has this section been omitted from the scan?
There was a problem hiding this comment.
Maybe it's due to angle brackets?
There was a problem hiding this comment.
Apparently they were originally omitted from ZAP because callback URLs are not real scannable endpoints on this API.
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-20515 |
Co-authored-by: Ian Hodges <ian.hodges1@nhs.net>
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-20515 |
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-20515 |
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-20515 |
4 participants
Summary
The use of angle brackets (
<and>) in placeholders for client-provided callback endpoint URIs has caused problems with the pages for those endpoints and links to them which are embedded in markdown.Reviews Required
Checklist