Jakub wrote:
> I'm just writing example for my Scheme interpreter called LIPS and I would
> like to use JavaScript fetch API to get title of a website, but to be able to
> do that I need website that support CORS. It would be nice if website is
> related to Scheme. I was thinking about one of scheme.org sub domains or the
> main domain itself.
>
> Do you plan to support CORS in the near future. It would be nice if main
> domain support CORS is I can use:
>
> (title "https://scheme.org")
>
> and see some nice title like "Scheme Programming Language".
>
> It will probably be awhile until the website will be running so I thought,
> maybe just setup example.scheme.org that people will be able to use instead
> of example.com in code examples (example.com don't support CORS
> unfortunately).
>
> example.scheme.org can be just simple S-Expression with text/plain like
>
> ((language . "scheme"))
>
> HTML site similar to example.com or website that return JSON.
>
> For my use case I would prefer normal html website, because I will be able to
> showcase Regular Expressions in LIPS Scheme (used to extract the title).
>
> I can create example website, every simple with just title and explanation
> that this is example website. I can create something based on example.com.
>
> But there is need to create sub domain and host it somewhere, There is
> no need for extra server because it will be just single file.
>
> What you think?

Sorry, this mail fell through. Does something need to be done at
scheme.org's end (in server configuration, HTML, or otherwise) to make
CORS work, or would you just tell the CORS headers on the Lips site to
trust scheme.org?