Skip to content

Commit 55225c6

Browse files
authored
Mention privacy risks of CORS proxies (#113)
* Update cors.md * Update cors.md
1 parent f9da1b7 commit 55225c6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/website/cors.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ CORS is the way that a website declares whether they want other websites to be a
2727
It depends on what the URL is for.
2828

2929
- **Switch to a different URL:** If the URL is just being used to host static files, find another host that supports direct downloads and CORS. If one API doesn't support CORS, check if a competitor's API does.
30-
- **Use a CORS proxy:** Instead of asking your browser to access a website directly, you can ask another server (called a CORS proxy) to access that website on your behalf and then send back the response but allowing CORS. There are many public CORS proxies that you can find online, but they tend to be short lived as they are expensive to operate and heavily abused. TurboWarp does not currently run its own CORS proxy.
30+
- **Use a CORS proxy:** Instead of asking your browser to access a website directly, you can ask another server (called a CORS proxy) to access that website on your behalf and then send back the response but allowing CORS. There are many public CORS proxies that you can find online, but they tend to be short lived as they are expensive to operate and heavily abused. CORS proxies can also spy on your project's web requests, as well as tamper with them. This can often be problematic. TurboWarp does not currently run its own CORS proxy.
3131
- **Switch to TurboWarp Desktop:** The desktop app has an option to bypass CORS. See below.
3232

3333
## Desktop app {#desktop}

0 commit comments

Comments
 (0)