-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
in POST v2/subscriptions if notification httpCustom url has invalid value the subsc is created #2280
Comments
Re-tested in the CB version. It issue still fails and returns
|
Fixed in PR #2815. Please @iariasleon check (once the PR gets merged). |
CB version used:
LGTM to the first and third datasets
But the second dataset continues to failing:
|
@iariasleon pls clarify which url in the second dataset is the case causing the problem (there are around 30-40 individual urls in that dataset ;)? |
All these wrong url are failing (They return a 201 instead of a 400): Second dataset with the same behavior
|
Could have been fixed by PR #2855. Please @iariasleon re-check. Take into account that some of the examples you use (http://1.1.1.1.1) correspond actually to valid URLs when the string is interpreted as hostname and not ip. |
Re-tested and only these tests are failing:
And about the reference used:
|
The function that verifies the validity of the hostnames isn't 100% correct. |
in POST v2/subscriptions if notification httpCustom url has invalid value the subsc is created
dataset used (replace these values into
url
field in request below)Second dataset with the same behavior
Third dataset:
subscription request
request response
mongo docs
Expected response
The text was updated successfully, but these errors were encountered: