When I open https://src.fedoraproject.org/rpms/python-requests/blob/rawhide/f/system-certs.patch and click on "History" button, I get HTTP/403. I've tried f43 branch with the same result.
Fix it, please, if it's an infra bug. If not, I can report it to Pagure instead.
Rather soon, if possible.
Metadata Update from @zlopez: - Issue assigned to zlopez - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
I thought that this is just a rule in httpd conf because of AI scrapers. But I couldn't find anything and at first glance I don't see anything wrong with the repository either. But I tried few other files in the repository and all of them are throwing 403 when trying to show up history of the file and not only in this repository, it seems the 403 is persistent when trying to look at the history of any file on src.fedoraproject.org.
Metadata Update from @zlopez: - Assignee reset
This was deliberately set by me in ansible commit https://pagure.io/fedora-infra/ansible/c/ea1a9a5b6ba8ae1c1d261a3b0a3905bccadc59f3?branch=main
Yes, it was due to scrapers hitting that endpoint really really hard.
I suppose we could try reopening history, as it was less trouble than blame. I am pretty against reopening blame tho.
I didn't expected it to be blocked at the proxy level. Thanks for pointing that out.
I opened https://pagure.io/fedora-infra/ansible/pull-request/3020 to re-enable the history endpoint. I will wait for @kevin giving it +1 before merging it.
+1 sure, we can try it... but be ready to revert.
Metadata Update from @zlopez: - Issue assigned to zlopez
The history is now re-enabled. And everything seems OK for now. Let me close this as fixed.
Metadata Update from @zlopez: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)