feat(android,ios): Support for passing in request headers

[sanketmehta7]

Support for passing request headers only for android.
User need to pass comma separated headers, with their key, values separated by :
Eg: cordova.InAppBrowser.open("http://apache.org", "_self", 'location=no','custom-h1:asd,h1:xyz');

[TakkuzOld]

This would be really useful, mostly on WP8, (if it will be possible) where file-transfer fails.

[olivercs]

Very useful when you have to send a token or Authorization header to access to a resource.

[kodeine]

@sanketmehta7 can you please fix the conflicts so this can be merged?

[ghost]

Would there be any chance for ios as well?

[mrtnjln]

Any news on this ?
I can't build on Xcode (missing .h declaration for navigateToNew method).

[ramses80]

hellow.julymartin.can.you.herme.or.not

[infil00p]

This is an API change and should be discussed on the list, or at the very least have a JIRA issue attached to it. Also, the conflicts are definitely going to prevent this from getting merged as-is.

[rdksgit]

Does this work with ios

[daveshirman]

@rdksgit Nope, using this forked version causes the iOS build code 65. So basically unless the developer can fix the reason why it causes the build to fail, this plugin is not production ready.

Note: you won't see the build error on Android build, just iOS.

@sanketmehta7 Thanks for this plugin very much. Is there any chance that you will be able to sort the build (causing issue Error 65) any time soon please?

Feedback would be greatly appreciated, thank you.

[janpio]

Hey @sanketmehta7 , there seems to be a merge conflict now. Could you maybe fix this? Thanks.

[janpio]

Hard conflicts, which is not a big surprise after so long.
As the feature itself still looks interesting, this should probably be resurrected as a new PR.

[Aiuspaktyn]

Any news about this PR?

[sanketmehta7]

will try to create new PR from latest code

[kasp1]

In the meantime, if anyone needs to access an HTTP auth protected site/resource, you can include the creds in the URL, e.g.:

https://username:password@host.name/...

It's got me over this issue for now, so it could help someone else as well.

[iantearle]

will try to create new PR from latest code

Did you have any luck with this?

[sawaca96]

Any update?

[lubbo]

Hard conflicts, which is not a big surprise after so long.
As the feature itself still looks interesting, this should probably be resurrected as a new PR.

@janpio What about #1024 ?
I'm not changing API but using the options with json and base64 encoding for headers and cookies as well.
Let me know.
Cheers!