raw.githubusercontent.com does not update

[GladistonXD]

Select Topic Area

Bug

Body

I can't update old files with the same name.

[2Abendsegler]

Hi,

I can confirm that. I have the same problem.

In the meantime I have deleted my two main branches "master" and "collector" in my repository. Nevertheless, the raw.githubusercontent.com links are still there. This is only the case with these two special branches. With other branches, the file under the raw.githubusercontent.com link is also immediately deleted when deleting the branch. I can create the two branches again from another one, but the raw.githubusercontent.com are not updated.

Some of the raw.githubusercontent.com links are large scripts (1.2 MB). This may have something to do with the problem, because it always takes a while before the merge of a branch is also visible in the raw.githubusercontent.com link.

To Reproduce:

• Go to repository: https://github.com/2Abendsegler/GClh
  You can see there is only one branch "master2".
• Call raw.githubusercontent.com link to a script in deleted branch "master": https://raw.githubusercontent.com/2Abendsegler/GClh/master/gc_little_helper_II.user.js
• And call raw.githubusercontent.com link to a script in deleted branch "collector": https://raw.githubusercontent.com/2Abendsegler/GClh/collector/gc_little_helper_II.user.js

Thanks for helping.

[cyroxx]

Same here.

The file https://github.com/robert-koch-institut/SARS-CoV-2-Nowcasting_und_-R-Schaetzung/blob/main/Nowcast_R_aktuell.csv was updated by this commit: robert-koch-institut/SARS-CoV-2-Nowcasting_und_-R-Schaetzung@c9fae56

But the raw file still contains the old version, even though the commit is more than 6 hours old now:
https://raw.githubusercontent.com/robert-koch-institut/SARS-CoV-2-Nowcasting_und_-R-Schaetzung/main/Nowcast_R_aktuell.csv

[2Abendsegler]

And it is only a small file. :(
In the meantime I reported a bug in the support area. However, the ticket for this is probably not visible to everyone. There are no results yet.

[cyroxx]

I also filed a bug report, ticket #2008051.

[copyminter]

We are seeing the same issue with our files: https://github.com/teia-community/teia-report/blob/main/restricted.json
An update 3 hours ago is still not showing up in the raw version. I attempted to update the list to see if that triggers anything but it is still stuck on an old version from yesterday.

[copyminter]

This list that was updated 6 hours ago is now up to date with raw access. Another list I updated later still has the older updates.

[copyminter]

Another update 11 hours ago is still not showing up in the raw version. It used to take 5-10 mins for any updates to be reflected via raw.

[2Abendsegler]

Another update 11 hours ago is still not showing up in the raw version. It used to take 5-10 mins for any updates to be reflected via raw.

That can not be. New CEO Nat Friedman said after the acquisition that he wanted to make GitHub better for developers. 😂

[FlorianWilhelm]

Hi, I can confirm this bug. For me it's the following two files:

• https://github.com/FlorianWilhelm/pytanis/blob/main/docs/assets/images/logo.svg
• https://raw.githubusercontent.com/FlorianWilhelm/pytanis/main/docs/assets/images/logo.svg

Which should show the same logo but the latter one still shows the old version.

[alams154]

Also confirming the bug:

• XML File
• XML File (raw)

File was changed about a hour ago and still has not updated the version available at raw.githubusercontent.com

[zezzy63]

Also confirming the bug:
https://github.com/zezzy63/fluffy-waddle/blob/main/Unrevealed.LoaderHash.txt
https://raw.githubusercontent.com/zezzy63/fluffy-waddle/main/Unrevealed.LoaderHash.txt

[Plextora]

I'm also confirming this bug as well. All files I try to update in the Imrglop/Latite-Releases repo do not update. For example, a commit that updates the injector file does not go into effect on raw.githubusercontent.com

[niklas389]

Same here:
https://github.com/niklas389/lemonkebab_Nameless_A13/blob/master/update.json
https://raw.githubusercontent.com/niklas389/lemonkebab_Nameless_A13/master/update.json

[LeonmDK3]

Guess it might have something to do with this? "cache-control | max-age=86400"
Not sure but that would mean to cache the file for 24 hours instead of 600 sec which would be 5 minutes.
Also affecting my repo: https://github.com/LeonmDK3/EmergencyAssistSystem/blob/main/unames.txt

[GladistonXD]

That could be right default repositories apparently is "max-age=300" repositories with a delay of up to 24h show 86400 in response

[real-yfprojects]

I don't know why but wget gets the right version, while my firefox still displays the old one although no-cache is enabled in the dev options.

[wiegerthefarmer]

Confirming I have the same bug. I made a typo in the one yaml file that our system pulls from raw.... and now my jupyter hub is down. Lol. Sigh.

[wiegerthefarmer]

CDN is now delivering the correct version.

[BangDroid]

Pulling my freakin hair out over here (what's left of it!). Usually when you have a thought like, GitHub is "broken", you are wrong and the problem is you. But it's nice (worse?) to know that occasionally, GitHub is indeed at fault.

[2Abendsegler]

Off topic:

Pulling my freakin hair out over here (what's left of it!).

😂

But it's nice (worse?) to know that occasionally, GitHub is indeed at fault.

That's not decided yet.
Maybe because of the ever-increasing traffic, that's just the way it's intended. That's called deceleration. So like in the Stone Age, when you had to ask whether an e-mail had already arrived.

[BangDroid]

I'm not the one using the term bug, see above. All I meant is that I'm glad it's not just me, because 9/10 it is.

[wiegerthefarmer]

Right? I was working on my laptop tethered to my phone driving yesterday. I thought about it all night. Come into work early today to continue the work and then find others having the same issue. I feel much better.

[wiegerthefarmer]

Well exactly 24 hours later, my changes went through.

[Juanescacha]

I don't know if I'm right but I faced the same issue with an image from my repo on the Repo Readme, I changed it and didn't update after like 48h so I think its just a matter of time to update, and github is not constantly updating the changes to the urls, you will have to wait some time...

[GladistonXD]

The only way that "resolve" was changing the name of the repository, I will have to redirect the updates to the new name and after 24 hours change the name of the repository. 😑

[auwsom]

Could you clarify.. so change repo name works, but only after 24hrs (assuming because of the cache mag-age delay above), and you will have to redirect to the new name, but why "after 24 hours, change the name of the repository"? Why change it after 24 hours? Do you mean, change the name in the redirection after waiting 24hrs? (no, that wouldnt help.. idk)
Thx

[GladistonXD]

Changing the name of the repository resolves it immediately, but I have to wait 24 hours to redirect the repository updates to the new name, this is a specific case of mine, but changing the name of the repository apparently resolves it immediately.

[auwsom]

thanks, below I comment that copying the file to a new name also works.. have not tested replacing the original one with it.. but certainly less dramatic in complexity than changing a repo name if it is connected to other things. cheers.

[karsiong]

lolz.....anyone tag GitHub staff here let them know the issue, I think they didn't realize the issue after so many days.

[2Abendsegler]

I have a free account. That probably applies to most people here. Our opinions probably don't carry much weight. It would certainly help if paying users made themselves known to GitHub, if they are affected by the problems at all.

[auwsom]

This is very frustrating. I use the raw content to download basic settings for Linux dotfiles. Has been working for years.. now broken.

https://stackoverflow.com/questions/53491680/curl-and-wget-not-getting-the-latest-committed-file-from-github

For some reason the 'raw' tab on GH website and URL shows the correct info.. but wget and curl do not retrieve it. How can this be?

Also weird, I can make a copy, git commit, add and push it, and the new file curls nearly instantly and correctly. (mystified)

[GladistonXD]

I did some tests the problem is now in the default encoding, Accept-Encoding: gzip , if you use Accept-Encoding: deflate it updates to the new version.

[heqds]

How do I use that encoding? I am having this problem 3 weeks later.

[GladistonXD]

These are the encodings of a request, you can send a get with headers on any platform.

curl -sH 'Accept-encoding: deflate' http://example.com/...

[heqds]

Where do I put that?

[GladistonXD]

On any request, take a look at this thread there may be better support. #46691

[kristoftorok]

I have the same problem with DNS block lists.

[Mandark-droid]

+1 getting same issue while trying to download. https://raw.githubusercontent.com/iterativv/NostalgiaForInfinity/main/NostalgiaForInfinityX2.py

Please fix.

[antn]

We are not setting a longer cache value for raw files. You're probably seeing the default cache value of 5 minutes. Please wait for the cache to be cleared.

[auragit]

Adding ?token=$(date +%s) to the end of the URL worked for me.

[MichaelTiemannOSC]

Wow! Somebody knows how to read the docs closely!!

[FarisFarley]

Now its working..

I just updated my repository from desktop git and it updated immediately but in (raw-github-user-content) it updated after 10 minutes.
Just note that when ever you update also change the description before you commit and when you push select the latest description then select the file you made changes and then push and it worked fine.

[avivash]

Same issue over here:

https://github.com/oddsdk/blockpaperscissors/blob/main/hamb.fundring

https://raw.githubusercontent.com/oddsdk/blockpaperscissors/main/hamb.fundring

[Harshkesharwani]

https://raw.githubusercontent.com/nltk/nltk_data/gh-pages/packages/tokenizers/punkt.zip
I could not download this please give me the solution

[MichaelTiemannOSC]

See nltk/nltk_data#202. Also see issues files in nltk/nltk that reference same problem.

[Xiaod0ng]

I made a minor update to my json file, but the raw file is not updated until 10 mins later.

[farishajdarpasic]

Same issue. I pushed, but raw is not updated

[kleinlennart]

Sad that this hasn't been fixed...
I'm using raw.githubusercontent.com to include JS scripts, and this bug is completely ruining my workflow.

[MTDickens]

Same issue here. Why don't Github team fix this? Or at least give us some replies...

But adding ?token=$(date +%s) to the end of the URL worked for me.

[gchartier]

I think this doesn't work anymore as it was working for me and now I just get 404's

[koder101]

I can confirm that the issue still persists.

[Map987]

edit a text file , and the taw textfile isn't change real time .

[marionzr]

This is how I solved it yesterday.

To force GitHub to give you the latest version of a file without caching, you can append a query parameter to the URL. This query parameter ensures that GitHub treats the request as a new one, bypassing any cached version.

Example

https://raw.githubusercontent.com/marionzr/file-share/refs/heads/main/content.csv?timestamp=20250212

The timestamp=20250212 (or any unique value) ensures the URL is seen as different every time you request it, so GitHub will fetch the latest version of the file. So, alternatively, you can use ?cache_bust=<random_value> to achieve the same effect.

https://raw.githubusercontent.com/marionzr/file-share/refs/heads/main/content.csv?cache_bust=banana123

If that solves the problem for you, consider giving a look into my projects and giving them a star!

[sagarchaulagai]

its not working for me

[virus-rpi]

it worked once and then not anymore after trying again later so it might have been a coincide the first time

[suzuki-shunsuke]

We faced the similar issue.

• Checksum verification fails for aqua-registry (Failed to download correct registries from raw.githubusercontent.com) aquaproj/aqua#4068

We created a support ticket and GitHub is intestigating the issue.
As a workaround, we could get the correct file by specifying full length commit SHA.