Fix CORS blocking and update Google template target resources#359
Draft
Fix CORS blocking and update Google template target resources#359
Conversation
- Add missing Google domains to targetResources in google.com_gsuite.json (recaptcha.net, fonts.googleapis.com, play.google.com, apis.google.com, etc.) - Strip Cross-Origin-Resource-Policy, Cross-Origin-Opener-Policy, and Cross-Origin-Embedder-Policy headers that block cross-origin resource loading - Add default Access-Control-Allow-Methods and Access-Control-Allow-Headers response headers for CORS preflight request support Co-authored-by: drk1wi <2052966+drk1wi@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add support for a new HTTPS proxy
Fix CORS blocking and update Google template target resources
Feb 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Google login pages fail to fully render (only email field, no password step) because modern Google domains are missing from
targetResourcesand cross-origin headers block resource loading.Template update (
templates/google.com_gsuite.json)recaptcha.net,www.recaptcha.net,people-pa.googleapis.com,fonts.googleapis.com,fonts.gstatic.com,signaler-pa.clients6.google.com,play.google.com,apis.google.com,lh3.googleusercontent.com,myaccount.google.com,www.googleapis.comCORS handling (
core/proxy.go)Cross-Origin-Resource-Policy,Cross-Origin-Opener-Policy,Cross-Origin-Embedder-Policyheaders alongside existing security header strippingAccess-Control-Allow-MethodsandAccess-Control-Allow-Headerson responses whenOriginis present, so CORS preflight requests succeed:These only apply as defaults — upstream values are preserved when present.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.