This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
Padding for Subscription Locked endpoint causes bogus 400-201 error #466
Comments
jrconlin
added a commit
that referenced
this issue
May 9, 2016
Since fernet passes it's content through base64 handling, it's just as picky about padding as other base64 instances. For now, strip padding from outbound endpoints and reapply it (if needed) to inbound endpoints. Closes #466
jrconlin
added a commit
that referenced
this issue
May 11, 2016
Since fernet passes it's content through base64 handling, it's just as picky about padding as other base64 instances. For now, strip padding from outbound endpoints and reapply it (if needed) to inbound endpoints. Closes #466
jrconlin
added a commit
that referenced
this issue
May 11, 2016
Since fernet passes it's content through base64 handling, it's just as picky about padding as other base64 instances. For now, strip padding from outbound endpoints and reapply it (if needed) to inbound endpoints. Closes #466
jrconlin
added a commit
that referenced
this issue
May 11, 2016
Since fernet passes it's content through base64 handling, it's just as picky about padding as other base64 instances. For now, strip padding from outbound endpoints and reapply it (if needed) to inbound endpoints. Closes #466
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There is a problem with subscription locked endpoints fernet decoding if the padding is altered.
The text was updated successfully, but these errors were encountered: