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
This postman call will produce http status code 500, and message of "invalid character '"' in \u hexadecimal character escape", with this error message, it shouldn't be status code 500, but status code 400.
🔥 Exception or Error
{
"apiVersion": "v3",
"message": "invalid character '"' in \u hexadecimal character escape",
"statusCode": 500
}
🌍 Your Environment
use compose-builder command make run no-secty ds-virtual to bring up EdgeX system
EdgeX Version [REQUIRED]:
3.1
Anything else relevant?
The text was updated successfully, but these errors were encountered:
🐞 Bug Report
Affected Services [REQUIRED]
support-notification
Is this a regression?
no
Description and Minimal Reproduction [REQUIRED]
use compose-builder command
make run no-secty ds-virtual
to bring up EdgeX systemOn postman:
POST http://localhost:59860/api/v3/subscription
JSON body: (note: name has value of "\u")
{
"subscription": {
"name": "\u",
"channels": [
{
"type": "REST",
"host": "fuzzstring",
"port": 1,
"path": "fuzzstring",
"httpMethod": "fuzzstring"
}
],
"categories": [
"fuzzstring"
],
"labels": [
"fuzzstring"
],
"description": "fuzzstring",
"receiver": "fuzzstring",
"resendLimit": 1,
"resendInterval": "fuzzstring",
"adminState": "LOCKED"
},
"requestId": "3a4cd2dd-8b9e-4b5b-a079-5048a78ef371",
"apiVersion": "v3"
}
This postman call will produce http status code 500, and message of "invalid character '"' in \u hexadecimal character escape", with this error message, it shouldn't be status code 500, but status code 400.
🔥 Exception or Error
{
"apiVersion": "v3",
"message": "invalid character '"' in \u hexadecimal character escape",
"statusCode": 500
}
🌍 Your Environment
use compose-builder command
make run no-secty ds-virtual
to bring up EdgeX systemEdgeX Version [REQUIRED]:
3.1
Anything else relevant?
The text was updated successfully, but these errors were encountered: