FWIW same fork works on src.stg.fp.o

@sharkcz can you try it again, it worked for me: https://src.fedoraproject.org/fork/vivekanand1101/rpms/firefox

It takes some time. Mine was quicker than usual

and https://src.fedoraproject.org/do_fork/rpms/firefox will give bad request because, it accepts POST request and by going to that url will be GET

After refreshing the main firefox page the forking worked.

After refreshing the main firefox page the forking worked.

are you fine? should i close this then?

I suspect there is a deeper issue, would prefer to get an answer from @pingou before closing.

and https://src.fedoraproject.org/do_fork/rpms/firefox will give bad request because, it accepts POST request and by going to that url will be GET

then pagure is doing something wrong, because that's what I got when clicking on the "Fork" button

The question is basically, were you logged in before you click on Fork?

What I think could happen is: you click on fork, you were logged out, it takes you to ipsilon(id.fedoraproject.org), you have a kerberos session open so it uses it to auth you, it redirects you to the pagure URL you were calling and that redirect cannot be a POST and thus is a GET.

Can you reproduce this easily? If more people run into this maybe we could consider accepting GET and redirecting to a page that doesn't error but shows an error message, but if it was a one-of thing then the work needed is less important/urgent.

I don't recall all the details, but I'm sure I was logged in before doing the fork. Or maybe I logged in when the Firefox main page has been displayed, but still before the forking.

Has this ever been reproduced?

I just forked a repo on dist-git this morning and it worked fine.

nope, it likely required some special circumstances

Ok I'm going to close this for now hoping it never gets replicated :)