Link directly to .css file in a repo? #3675

New Issue

GiteaMirror · 2025-11-02T05:21:23-06:00

GiteaMirror commented

2025-11-02 05:21:23 -06:00

Originally created by @STaRDoGG on GitHub (Jul 25, 2019).

I'd like to do what the title says, from within a html file, but even when linking to the 'raw' file, it's mime type is transferred as text rather than css.

On GitHub you have to make a GitHub "Page" in order to link directly to a CSS file and have it transferred as the CSS mime type, but Gitea doesn't have a "pages" feature (which if fine by me), so I'm wondering if there's some way we can 'crowbar' this into happening for our own local Gitea server? It'd be kinda cool if there was some check-box or something on the file in the repo to set it's mime type ... or something.

I know I could just move my repo to Github and create a github page to do this, but I'd like to just be able to do so from my own repo server.

Originally created by @STaRDoGG on GitHub (Jul 25, 2019). I'd like to do what the title says, from within a html file, but even when linking to the 'raw' file, it's mime type is transferred as text rather than css. On GitHub you have to make a GitHub "Page" in order to link directly to a CSS file and have it transferred as the CSS mime type, but Gitea doesn't have a "pages" feature (which if fine by me), so I'm wondering if there's some way we can 'crowbar' this into happening for our own local Gitea server? It'd be kinda cool if there was some check-box or something on the file in the repo to set it's mime type ... or something. I know I could just move my repo to Github and create a github page to do this, but I'd like to just be able to do so from my own repo server.

GiteaMirror added the type/question reviewed/wontfix labels 2025-11-02 05:21:23 -06:00

GiteaMirror closed this issue

2025-11-02 05:21:23 -06:00

GiteaMirror commented

2025-11-02 05:21:24 -06:00

@silverwind commented on GitHub (Jul 26, 2019):

If you have nginx or similar, you could regex-match the URL an change the content-type header there. Otherwise, maybe we want to support something like ?content-type=type but I'm not sure on the security implications of client-controlled content-type.

@silverwind commented on GitHub (Jul 26, 2019): If you have nginx or similar, you could regex-match the URL an change the content-type header there. Otherwise, maybe we want to support something like `?content-type=type` but I'm not sure on the security implications of client-controlled content-type.

GiteaMirror commented

2025-11-02 05:21:24 -06:00

@gary-kim commented on GitHub (Jul 29, 2019):

If you have nginx or similar, you could regex-match the URL an change the content-type header there. Otherwise, maybe we want to support something like ?content-type=type but I'm not sure on the security implications of client-controlled content-type.

Sounds very dangerous. Since the file is hosted under the same domain as Gitea, this is an XSS vulnerability.

I don't think there is a safe way to do this without requiring admins to point two domains at Gitea.

@gary-kim commented on GitHub (Jul 29, 2019): > If you have nginx or similar, you could regex-match the URL an change the content-type header there. Otherwise, maybe we want to support something like `?content-type=type` but I'm not sure on the security implications of client-controlled content-type. Sounds very dangerous. Since the file is hosted under the same domain as Gitea, this is an XSS vulnerability. I don't think there is a safe way to do this without requiring admins to point two domains at Gitea.

GiteaMirror commented

2025-11-02 05:21:24 -06:00

@stale[bot] commented on GitHub (Sep 27, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Sep 27, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:21:24 -06:00

@stale[bot] commented on GitHub (Nov 29, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Nov 29, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:21:24 -06:00

@lunny commented on GitHub (Nov 29, 2019):

As @gary-kim said.

@lunny commented on GitHub (Nov 29, 2019): As @gary-kim said.

GiteaMirror referenced this issue

2025-11-02 11:38:45 -06:00

[PR #18] [MERGED] Fix 500 error caused by deleted users on issues (#3675) #15095

GiteaMirror referenced this issue

2025-11-02 12:27:03 -06:00

[PR #3895] [MERGED] Add option to use paged LDAP search when synchronizing users #17131

Sign in to join this conversation.