HTTP Request Origins set to LocalHost

[ehorodyski]

This plugin looks like it changes the HTTP request origin header from file:// to localhost:8080. This is breaking a lot of calls I'm trying to make to APIs that are not CORS enabled, and do not whitelist localhost as an entry.

Can anyone provide some insight?

[manucorporat]

It is not possible to bypass CORS in WKWebView. You have to implement CORS in your server whitelisting localhost:8080 or you can use the HTTP cordova plugin https://ionicframework.com/docs/native/http/

I recommend to implement CORS in your server though

[JiaLiPassion]

Hi , Mr. Manu MA Could you check my PR, #115, is it the correct direction? thanks . Jia Li

…

On Fri, May 19, 2017 at 9:52 PM, Manu MA ***@***.***> wrote: It is not possible to bypass CORS in WKWebView. You have to implement CORS in your server whitelisting localhost or you can use the HTTP cordova plugin https://ionicframework.com/docs/native/http/ I recommend to implement CORS in your server though — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#137 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABYDD53GLbHa1vYvFqSULWHSpPizN-l6ks5r7ZCmgaJpZM4NfVJr> .

[ehorodyski]

@manucorporat -- Would it come into consideration to let consumers decide to mask their origins, from null or localhost to something configurable?

There are many APIs available that are not CORS enabled that this plugin is preventing us from using. When building for web there's many options to proxy to mask localhost as origin, but we've found a lot of 3rd party APIs we want to use are blocking based on origin.

Then it's like, do we drop the plugin, and lose the latest web advances (like display:sticky in some cases, and Ionic's infinite scroll), or try to create a wrapper around an API, congesting the end-user.

Is there a win-win scenario where I can call Yelp and have Ionic Sticky Headers too?