Cannot access files or folders inside folder named "LServer" on Chrome #3662

New Issue

GiteaMirror · 2025-11-02T05:20:57-06:00

GiteaMirror commented

2025-11-02 05:20:57 -06:00

Originally created by @FINDarkside on GitHub (Jul 24, 2019).

Gitea version (or commit ref): 1.10.0+dev-85-g635e7b38b
Git version: 2.21.0.windows.1
Operating system: Windows 10
Database: Whatever is in try.gitea.io
Can you reproduce the bug: https://try.gitea.io/TestUser3256/Test

Description

Files inside folder named "LServer" cannot be accessed with Chrome 75. Trying to open any file or folder inside it gets you this:

This site can’t be reached 
The web page at https://try.gitea.io/TestUser3256/Test/src/branch/master/LServer/test.txt might be temporarily down or it may have moved permanently to a new web address.
ERR_FAILED

Steps to reproduce:

Open https://try.gitea.io/TestUser3256/Test with Chrome
Open LServer folder
Try to open the txt file or subfolder inside LServer

Seems to be caused by service worker, as removing or bypassing it makes everything work again.
Seems to work fine with Firefox 68 and Edge 44

Originally created by @FINDarkside on GitHub (Jul 24, 2019).   - Gitea version (or commit ref): 1.10.0+dev-85-g635e7b38b - Git version: 2.21.0.windows.1 - Operating system: Windows 10 - Database: Whatever is in try.gitea.io - Can you reproduce the bug: https://try.gitea.io/TestUser3256/Test ## Description Files inside folder named "LServer" cannot be accessed with Chrome 75. Trying to open any file or folder inside it gets you this: ``` This site can’t be reached The web page at https://try.gitea.io/TestUser3256/Test/src/branch/master/LServer/test.txt might be temporarily down or it may have moved permanently to a new web address. ERR_FAILED ``` ## Steps to reproduce: * Open https://try.gitea.io/TestUser3256/Test with Chrome * Open LServer folder * Try to open the txt file or subfolder inside LServer Seems to be caused by service worker, as removing or bypassing it makes everything work again. Seems to work fine with Firefox 68 and Edge 44

GiteaMirror added the issue/not-a-bug label 2025-11-02 05:20:57 -06:00

GiteaMirror closed this issue

2025-11-02 05:20:57 -06:00

GiteaMirror commented

2025-11-02 05:20:58 -06:00

@zeripath commented on GitHub (Jul 24, 2019):

This is very interesting.

The request doesn't even get out of the browser. If you ctrl-F5 it works.

I think this is an issue with our recent upgrade to jquery 3.

@zeripath commented on GitHub (Jul 24, 2019): This is very interesting. The request doesn't even get out of the browser. If you ctrl-F5 it works. I think this is an issue with our recent upgrade to jquery 3.

GiteaMirror commented

2025-11-02 05:20:58 -06:00

@FINDarkside commented on GitHub (Jul 24, 2019):

Added 3 additional folders to better demonstrate that it's somehow related to that specific folder name.

@FINDarkside commented on GitHub (Jul 24, 2019): Added 3 additional folders to better demonstrate that it's somehow related to that specific folder name.

GiteaMirror commented

2025-11-02 05:20:58 -06:00

@jolheiser commented on GitHub (Jul 24, 2019):

Short Answer

This is an ad-block issue. If you are using Chrome, I assume you are using uBlock or some derivative.

Currently the easiest way to fix the issue is to disable the ad-blocker for Gitea.

Medium Answer

In the EasyList filter there is a pattern for /lserver/* which is why it never even makes it to the browser.
As another example I found at random from that list /oascache/* you can see the same behavior in my test repo (https://try.gitea.io/jolheiser/Cache) when you click into OASCache and then test.txt

GitHub even displays some weird behavior. I suspect that they cache things differently so as to return a page, but it looks like some of their backend calls must fail.

@jolheiser commented on GitHub (Jul 24, 2019): ## Short Answer This is an ad-block issue. If you are using Chrome, I assume you are using uBlock or some derivative. Currently the easiest way to fix the issue is to disable the ad-blocker for Gitea. ----- ## Medium Answer In the `EasyList` filter there is a pattern for `/lserver/*` which is why it never even makes it to the browser. As another example I found at random from that list `/oascache/*` you can see the same behavior in my test repo (https://try.gitea.io/jolheiser/Cache) when you click into `OASCache` and then `test.txt` GitHub even displays some weird behavior. I suspect that they cache things differently so as to return a page, but it looks like some of their backend calls must fail. ![lserver](https://user-images.githubusercontent.com/42128690/61825676-749dce00-ae26-11e9-9b98-bc7f3fe87220.png)

GiteaMirror commented

2025-11-02 05:20:58 -06:00

@zeripath commented on GitHub (Jul 24, 2019):

I'm not sure that's there anything we can do from within Gitea to fix this so I'm going to mark this as invalid and close it.

@zeripath commented on GitHub (Jul 24, 2019): I'm not sure that's there anything we can do from within Gitea to fix this so I'm going to mark this as invalid and close it.

GiteaMirror commented

2025-11-02 05:20:59 -06:00

@richmahn commented on GitHub (Jul 25, 2019):

Interesting, I run adblocker and haven't modified it, yet I can open it.

@richmahn commented on GitHub (Jul 25, 2019): Interesting, I run adblocker and haven't modified it, yet I can open it.

GiteaMirror commented

2025-11-02 05:20:59 -06:00

@kolaente commented on GitHub (Jul 25, 2019):

It seems to work with ublock origin on Firefox mobile, if it's an adblock problem shouldn't it also be blocked regardless of the browser as long as they're using the same list?

@kolaente commented on GitHub (Jul 25, 2019): It seems to work with ublock origin on Firefox mobile, if it's an adblock problem shouldn't it also be blocked regardless of the browser as long as they're using the same list?

GiteaMirror commented

2025-11-02 05:20:59 -06:00

@jolheiser commented on GitHub (Jul 25, 2019):

@kolaente That would be my guess as well. I can't say I dug too much into which lists contain it or how that specific ad-blocker responds, I tested using Chrome with uBlock Origin.

It looks as though the list is actually in a repository over at https://github.com/easylist/easylist
If you search for lserver you'll find it in easylist_general_block.txt

EDIT: I just installed uBlock Origin on Firefox and I can now reproduce a similar error.

EDIT 2: Just did a fresh install of Firefox on my phone and installed uBlock Origin (Raymond Hill), still getting the corrupted content error.

@jolheiser commented on GitHub (Jul 25, 2019): @kolaente That would be my guess as well. I can't say I dug too much into which lists contain it or how that specific ad-blocker responds, I tested using Chrome with uBlock Origin. It looks as though the list is actually in a repository over at https://github.com/easylist/easylist If you search for `lserver` you'll find it in `easylist_general_block.txt` EDIT: I just installed uBlock Origin on Firefox and I can now reproduce a similar error. ![ublock_ff](https://user-images.githubusercontent.com/42128690/61904905-754d6780-aeed-11e9-97ec-287787ad36eb.png) EDIT 2: Just did a fresh install of Firefox on my phone and installed uBlock Origin (Raymond Hill), still getting the corrupted content error.

GiteaMirror referenced this issue

2025-11-02 12:24:44 -06:00

[PR #3662] [MERGED] Add label descriptions #17034

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#3662