Skip to content

Update config.fronting-groups.example.json#1263

Open
Shjpr9 wants to merge 2 commits into
therealaleph:mainfrom
Shjpr9:main
Open

Update config.fronting-groups.example.json#1263
Shjpr9 wants to merge 2 commits into
therealaleph:mainfrom
Shjpr9:main

Conversation

@Shjpr9
Copy link
Copy Markdown
Contributor

@Shjpr9 Shjpr9 commented May 17, 2026

  • Some minor tweaks to make Github work

We know that many fronting groups we used to use has been recently blocked.
This commit contains some changes to make Github work better, However, still some domains (like githubassets.com) must pass through Apps Script.
My tests show that these changes will make some actions like navigating through repositories faster and more smooth.
I'll try my best to scan and find working ips that are on Fastly edge and will make a PR in the future.

Thanks in advance

Copy link
Copy Markdown
Owner

@therealaleph therealaleph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the scan and the GitHub-focused testing. I cannot merge this shape yet because the PR changes the existing fastly group from a Fastly/PyPI edge to 185.199.109.215 + github.githubassets.com, while leaving the Reddit/Fastly/PyPI domains in that same group. That can regress non-GitHub hosts that currently rely on the Fastly group.

Please split the GitHub asset/fronting changes into a dedicated GitHub group, or keep the existing fastly group intact and only move/add GitHub domains where the SNI/IP pair is known to work. The file is valid JSON (jq empty passed), but the grouping semantics need to stay safe for the older domains.


Answered via LLM, Supervised @therealaleph

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants