-
-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove x-requested-with from headers #221
Comments
💎 $300 bounty • GoranSteps to solve:
Thank you for contributing to Cap-go/capacitor-inappbrowser! Add a bounty • Share on socials
|
Hey @goranlisak , thanks for the bounty, please give more detail, what is the current value sent? |
Currently the webview sends "x-requested-with" by default and puts app's ID as the value. I can change this value by setting custom headers in The problem that I experience is that I want to integrate a third party service through OpenID Connect authentication flow, but I automatically get redirected to the error page, instead of the login page. I used HTTP Toolkit to modify the request and found out that when this header is removed, then I get to the login page. Setting empty string, null, false, 0, invalid characters, etc, doesn't work. The only way for it to work is if the header is removed completely. |
I would love to attempt this: /attempt #221
|
One important question: is it ONLY the initial request that needs the “x-requested-with” header to be removed or is it all requests to this service/web page? |
@WcaleNieWolny thank you for attempting to solve this. It is all request. There's a few redirects in the login flow and this header needs to be removed from all of them. |
I will say, that at least on IOS I am not getting this problem. I will now test Android. |
I need an option to remove "x-requested-with" from headers when using WebView in Android and iOS. Setting an empty string is not enough for me. I would like to remove it completely.
It would be good if the completed feature had an option to remove any of the default headers, but the removal of "x-requested-with" is the priority.
It is also important that this header stays removed even as the user navigates to different URLs.
The text was updated successfully, but these errors were encountered: