-
Notifications
You must be signed in to change notification settings - Fork 25
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
CdnId seems to work, CdnKey not #17
Comments
That means that f84fdeb was incomplete. Got it reproduced now too, thanks for the report.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
I have chronic problems downloading attachments with the Whisperfish dev version.
There are both network-style timeout errors and 403 return codes.
My MO for rescue is to always run Whisperfish with logging on, hoping real hard all the
relevant information is being logged (that has not always been the case).
The steps to create a rescue script are here https://gitlab.com/rubdos/whisperfish/-/blob/rescue-operations/doc/rescue-instructions.rst
Once I've mangled the log file into a bash script, fingers crossed, attachments are downloaded.
The only file, now that the
CdnId
and theCdnKey
are introduced is the singleCdnId
one,no
CdnKey
is downloaded, it only returns 403.My hypothesis would be that these are not interchangeable. It would make sense that 403 is
returned instead of 404, to not leak whether or not files exist in the endpoint.
Is there something to my hypothesis? How would I go about decoding the string keys into
integer identifiers?
Thanks!
The text was updated successfully, but these errors were encountered: