Iceberg's https:// clones, fetches, pulls and pushes, and Metacello's github:// loads, go to this CORS proxy: each request goes to the proxy's URL followed by the host and the path of the repository, such as github.com/pharo-project/pharo.git. The proxy sees the code and any credentials that pass through it, so choose only one that you run or trust: the user name and token that a push asks for go only through My proxy, or straight to the host with None, never through the site's default. With None, the requests go to the repository itself, which works only for a server that lets this page in (CORS). This browser keeps your choice; a link cannot set it.
Pharo in the Browser with WebAssembly
The Pharo world, the Smalltalk environment, running in your browser on WebAssembly.
Key takeaways
A CORS proxy is used for Pharo browser requests, with options to trust a proxy or connect directly to the repository.
- Iceberg and Metacello use a CORS proxy for repository access.
- Users must choose a trusted proxy or connect directly to the repository.
- The browser retains the user's choice for future requests.
Summarised automatically by AI from the original article by Hacker News. AI can make mistakes, so check the original for details.
Story details
- Published
- By
- xkriva11
- Format
- Article
- Original
- massimo-nocentini.github.io ↗




