"403 Forbidden" when filtering for label on Issues #1767

ysfchn commented 2025年01月20日 11:50:38 +01:00

Comment

For this specific repository; Freeyourgadget/Gadgetbridge, if you try to go "Issues" and filter for a label, instead of it showing the filtered issues, it shows a blank page saying that the request is forbidden. Not sure what really causes that but I assume it is triggering something internally rather than a Forgejo issue so I wanted to post it here.

This URL triggers that error:

https://codeberg.org/Freeyourgadget/Gadgetbridge/issues?q=&type=all&sort=&labels=1222&state=open&milestone=0&project=0&assignee=0&poster=0&fuzzy=true

But this URL works as expected:

https://codeberg.org/Codeberg/Community/issues?q=&type=all&sort=&labels=102&state=open&milestone=0&project=0&assignee=0&poster=0&fuzzy=true

resim

It doesn't happen in any other repository that I've tried filtering issues on, for example on this repository it works as expected. It wasn't always like that before.

### Comment For this specific repository; [`Freeyourgadget/Gadgetbridge`](https://codeberg.org/Freeyourgadget/Gadgetbridge/issues), if you try to go "Issues" and filter for a label, instead of it showing the filtered issues, it shows a blank page saying that the request is forbidden. Not sure what really causes that but I assume it is triggering something internally rather than a Forgejo issue so I wanted to post it here. This URL triggers that error: <https://codeberg.org/Freeyourgadget/Gadgetbridge/issues?q=&type=all&sort=&labels=1222&state=open&milestone=0&project=0&assignee=0&poster=0&fuzzy=true> But this URL works as expected: <https://codeberg.org/Codeberg/Community/issues?q=&type=all&sort=&labels=102&state=open&milestone=0&project=0&assignee=0&poster=0&fuzzy=true>  It doesn't happen in any other repository that I've tried filtering issues on, for example on this repository it works as expected. It wasn't always like that before.

ashimokawa commented 2025年01月20日 22:39:17 +01:00

@ysfchn
Unfortunately, this is on purpose for that specific repository and known. I would prefer not to go into details, but it has to be that way for the time being..

@ysfchn Unfortunately, this is on purpose for that specific repository and known. I would prefer not to go into details, but it has to be that way for the time being..

ysfchn commented 2025年01月20日 23:30:11 +01:00

I would prefer not to go into details, but it has to be that way for the time being.

Understandable, no need for reasoning, I just thought it is something that shouldn't normally happen.

> I would prefer not to go into details, but it has to be that way for the time being. Understandable, no need for reasoning, I just thought it is something that shouldn't normally happen.