fix: 403 response from metal archives advanced searched endpoint #2
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Any search will result in a warning message, that the metal archives endpoint returns
403
Most likely it is only the header that need some adjustment.
When fixing this I'd appreciate adding tests, assuming the tests are already in experimental.
Metal archives started to use cloudflare:
There is a cloudflare bypass library that should still make it work without it being toooo much work. If this doesn't seem to work, the only option left would be to drop metal archives from the pages, because maintaining a cloudflare bypass would just be too much work.
If metal archives should be dropped, I'd send an email beforehand, asking them to provide an api, or expose theirs.
I don't seem to be able to figure out how to bypass cloudfairs. It also seems to be a constant updating task, which probably also requires me to run a browser in the back, and i don't wanna do that.