Remove reverse proxy from node example and rely on port and the domain parameter

[aeneasr]

Is your feature request related to a problem? Please describe.

The current set up uses a reverse proxy in the node example app to allow ORY Kratos to set cookies for that domain. However, cookies do not distinguish between ports (all ports of a domain will get the cookies) because, for example, TLS runs on 443 and HTTP on 80.

We also have control over the cookie domain now which would allow us to set a cookie for a TLD (example.org) from a subdomain (sub.example.org).

Describe the solution you'd like

• Remove the code from the selfservice example app
• Remove all references in the documentation for this set up
• Remove it from the quickstart set up
• Document a git commit message to alert people about this change as it will de-complicate their set up
• CORS configuration

[blakepettersson]

For this to work smoothly for client-side JS apps, we would also need to have the ability to set CORS headers in Kratos.

[aeneasr]

Yup, makes sense!

[wilcoschoneveld]

@aeneasr setting CORS headers in Kratos is not yet possible right?

[aeneasr]

#712