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
Hi.
Your schema validator is just fine, but i get an error while validating base64 encoded data.
Part of the schema is:
...
"signature": {
"type": "string",
"contentEncoding": "base64"
},
...
The JSON data is:
"signature": "cckZGzGyCvsX0RRKqc94VuFlX83/XLoZjvXMT0beE79PwVsBwjwyCYJqPEPZnz0RDvl0nnV3A5+T0GCZcJAsCuZUAWhvDz6ezHkU2eBGcdwRzoL7FdaVcGeVZSJeuzkl"
The exception is:
.../signature with "Content encoding failed on: base64. Reason: Illegal base64 character 2f"]
I have no idea why the JSON data is wrong. In my opinion it is a valid base64 string.
Do you have any idea?
Greetings from germany
Stefan
The text was updated successfully, but these errors were encountered:
Ah... I looked into your source.
I see you use a Base64.getUrlDecoder - why?
In this case you get the exception.
But using a normal Base64.getDecoder all works
Is there a special reason you use a UrlDecoder?
I thought that all kind of data can be encoded as Base64.
Hi.
Your schema validator is just fine, but i get an error while validating base64 encoded data.
Part of the schema is:
...
"signature": {
"type": "string",
"contentEncoding": "base64"
},
...
The JSON data is:
"signature": "cckZGzGyCvsX0RRKqc94VuFlX83/XLoZjvXMT0beE79PwVsBwjwyCYJqPEPZnz0RDvl0nnV3A5+T0GCZcJAsCuZUAWhvDz6ezHkU2eBGcdwRzoL7FdaVcGeVZSJeuzkl"
The exception is:
.../signature with "Content encoding failed on: base64. Reason: Illegal base64 character 2f"]
I have no idea why the JSON data is wrong. In my opinion it is a valid base64 string.
Do you have any idea?
Greetings from germany
Stefan
The text was updated successfully, but these errors were encountered: