How can I enable cookies in my iPhone Application that uses a UIWebView Window, so that my login system will work?
For sure start with
[NSHTTPCookieStorage sharedHTTPCookieStorage].cookieAcceptPolicy =
NSHTTPCookieAcceptPolicyAlways;
But, as mentioned by #JoelFan, the issue may be your User Agent string causing ASP.NET to attempt and fail at a cookieless login. Instead of a response that includes
Set-Cookie: .ASPXAUTH=really-long-hex-number
it returns a redirection to something like
Location: /(F(long-sorta-base64ish-looking-string))/
The default UIWebView user agent string is something like
User-Agent: Mozilla/5.0 (iPad; CPU OS 7_0_2 like Mac OS X) AppleWebKit/537.51.1 (KHTML, like Gecko) Mobile/11A501
but ASP.NET doesn't like this. Safari sends something like this:
User-Agent: Mozilla/5.0 (iPad; CPU OS 7_0_2 like Mac OS X) AppleWebKit/537.51.1 (KHTML, like Gecko) Version/7.0 Mobile/11A501 Safari/9537.53
Do the following early on, maybe in your AppDelegate.m
// DON'T try to reuse a UIWebView for this.
UIWebView *wv = [[UIWebView alloc] initWithFrame:CGRectZero];
// This webview has already decided to use the default user agent string.
// let's use javascript to get the existing user agent string
NSString *userAgent = [wv stringByEvaluatingJavaScriptFromString:#"navigator.userAgent"];
// let's tack on some stuff to make ASP.NET happy
userAgent = [userAgent stringByAppendingString:#" Version/7.0 Safari/9537.53"];
[[NSUserDefaults standardUserDefaults] registerDefaults:#{#"UserAgent": userAgent}];
// New UIWebViews inited after here will use the user agent string you made.
If the site you are logging into is an ASP.NET site, the problem may be due to the UIWebView sending an unrecognized User Agent. See Change User Agent in UIWebView (iPhone SDK)
Related
My app has UIWebViews, some loading sites where I need the desktop version of the site, some loading sites where I need the mobile version of the site.
So I set the user-agent to a desktop user-agent or a mobile user-agent to achieve this.
For example if I want a UIWebView to load a site's Desktop version I will simply run this code right before:
NSDictionary *dictionary = [NSDictionary dictionaryWithObjectsAndKeys:#"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36", #"UserAgent", nil];
[[NSUserDefaults standardUserDefaults] registerDefaults:dictionary];
The problem is that this of course is setting a NSUserDefaults variable, meaning for any UIWebView in my app that loads after this it will use the desktop user agent. I can just flip flop the NSUserAgent as needed between desktop and mobile and load accordingly but sometimes my app requires TWO UIWebViews to load at the same time, one mobile, one desktop.
Is there any way I can set the user-agent of a UIWebView specific to said UIWebView?
I'm assuming this is going to involve swizzling NSUrlRequest methods or something? I know very little about that stuff
The easy way, if possible, is to just use WKWebView instead of UIWebView. WKWebView exposes the user agent string as a property on the class itself (.customUserAgent, iOS9+). As an added bonus, JavaScript code running in the view will be faster and will use less battery power because the JavaScript can be precompiled into native code.
That said, if you have to stick with UIWebView for some reason, you could create an NSURLProtocol that intercepts all your app's HTTP requests and changes the field depending on the hostname in the URL. There are some examples of an NSURLProtocol on Apple's website. Start with that and tweak as needed.
Previous Title: Completely restarting a WKWebView after runtime
I am trying to implement a feature that allows for the user to request a desktop site of a URL in the WKWebView. If I'm not mistaken, this can only be done by resetting the UserAgent programatically, and then restarting (not sure what the correct term to use here is) the UIWebView altogether.
The UIWebView is setup in the Interface Builder and connected through an IBOutlet. Does anyone know where I would start? I am trying to implement this into a function.
Alright, so I figured out the simple answer to my question after a bit of debugging. You can literally set the custom user agent and reload the web page. Extremely simple. Here's some sample code via a function:
func requestDesktop() {
// Set Desktop UserAgent
let desktopAgent: String! = "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/602.3.12 (KHTML, like Gecko) Version/10.0.2 Safari/602.3.12"
webView.customUserAgent = desktopAgent
webView.reload()
}
I'm trying to request a desktop site using NSURLRequest. I found from How does Chrome's "Request Desktop Site" option work? that the solution seems to be to set the User-Agent header field to mimic a desktop User-Agent string. However, simply doing
NSURL *url = [NSURL URLWithString:#"http://www.facebook.com"];
NSMutableURLRequest *req = [NSMutableURLRequest requestWithURL:url];
[req setValue:#"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/534.53.11 (KHTML, like Gecko) Version/5.1.3 Safari/534.53.10" forHTTPHeaderField:#"User-Agent"];
[_webView loadRequest:req];
[self.view addSubview:_webView];
doesn't seem to lead me anywhere. My question is is this a correct User-Agent string I can use? Or is perhaps the request overriding the headers sometime after this?
UPDATE:
I tried visiting http://www.useragentstring.com/ instead of facebook to see the User-Agent string at the time of the request. It seems that it's
Mozilla/5.0 (iPhone; CPU iPhone OS 8_4 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) Mobile/12H141
instead of the string I set. This leads me to think that the request is overriding the User-Agent sometime during the request.
The UIWebView you're using to send the request is adding its own user agent, overriding yours. To change the user agent for your web view, try this
Change User Agent in UIWebView (iPhone SDK)
I can redirect based on user agent. But because of some weird problems on this work i am doing, i need to only redirect in-app uiwebviews to a sub folder or domain. Mobile Safari should be out of this redirect. Need help...
You can change the user agent of the in-app web views by writing to the standard user defaults with the "UserAgent" key. Here is an example,
[[NSUserDefaults standardUserDefaults] registerDefaults:#{
#"UserAgent": #"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17"}];
In my app, I use the following type of code to muck with the User-agent:
// Fake Firefox's user agent during web service's registration
NSDictionary *dictionary = [NSDictionary dictionaryWithObjectsAndKeys:#"Mozilla/5.0 (compatible; Windows; U; Windows NT 6.2; WOW64; en-US; rv:12.0) Gecko/20120403211507 Firefox/12.0", #"UserAgent", nil];
[[NSUserDefaults standardUserDefaults] registerDefaults:dictionary];
// Return to standard iOS user agent when web service registration is done
NSDictionary *dictionary = [NSDictionary dictionaryWithObjectsAndKeys:#"Mozilla/5.0 (iPhone; CPU iPhone OS 5_0 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A334 Safari/7534.48.3", #"UserAgent", nil];
[[NSUserDefaults standardUserDefaults] registerDefaults:dictionary];
Part of my app allows the user to register for a web service using its "sign up for an account" page, and the only way I could find to prevent its website from automatically launching a page which says "DOWNLOAD OUR APP INSTEAD!" is to muck with the user-agent string thusly. I've tried setting the User-agent in a NSMutableURLRequest but I have NOT gotten this to work at all. (Yes I have tried setting both "User-Agent" and "User_Agent" in the NSMutableURLRequest.)
I have heard that this might get your app rejected from Apple. Can anyone confirm or deny, or offer any comment? Thanks!
There are multiple apps on the App Store that fake the user agent as well.
All workarounds for setting the language of NSLocalizedString set a custom value for an Apple key in the NSUserDefaults as well
So I don't think Apple will reject your app.
We use custom user agents in our apps as a way for our servers to know that our app is calling - and to pass extra data, for example, whether the app has a retina screen. As long as you don't rely on this for security it works well. Nothing has ever been rejected as a result.