Repository navigation
Replies: 3 comments
|
We already have CORS proxy support see https://www.codenameone.com/developer-guide/working-with-javascript/#_using_the_cors_proxy_for_same_origin_requests |
0 replies
|
I think this is a different use case. normally the app is freestanding and can connect anywhere. In the javascript port it can only connect |
0 replies
|
This is the exact case. You get a war file or similar and can deploy it in a way where all requests get proxied through the core server and are allowed to connect anywhere. If you just want to limit connections to origin you can easily just do that. Just use |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
There's apparently no primitive that returns the host that javascript code is being loaded from. That's the only
host that subsequent http/s requests can go to. My apps need to be able toconstruct http requests and therefore
need to know what host they should be talking to.
One of the http request path builds a local cache of some data files (actually, they are .res files I moved out of
the app to shrink it to the size limit). Apparently browsers have a size limit for the "local" file system. So I expect
that this error is completely legitimate:
How does the javascript port deal with .res files, and how do they count against the size limits?
All reactions