Description
Loading content using file:// protocol has many restrictions. Does't integrate well with http content, cookies don't work, local storage is shared across all urls, Origin header (CRSF) doesn't work, CORS issues with files accessing each other (e.g. between directories), etc. Serving content using http://myapp/ url works similarly to serving content using custom scheme handler e.g. myapp:// (although scheme handlers are more configurable, see #50). It doesn't require running a server or running additional processes, it just maps requests. Currently scheme handlers are not implemented. There is available the wxpython-response.py example that can be found in README-examples.md and it shows how to use a Resource Handler along with web requests.
Related issues:
- Issue Expose Resource Manager API and a default custom scheme handler implementation #418 ("Expose resource manager API")
- Issue Scheme handler support (eg. myapp://) #50 ("Scheme handler support")