The certificate for this server is invalid

Question

I know that if I use following nsurlconnectiondelegate it will be fixed

– connection:willSendRequestForAuthenticationChallenge: – connection:canAuthenticateAgainstProtectionSpace

But I am trying to use

sendAsynchronousRequest:queue:completionHandler:

So you don't get the callback. I looked into apple docs it say following

If authentication is required in order to download the request, the required credentials must be specified as part of the URL. If authentication fails, or credentials are missing, the connection will attempt to continue without credentials.

I could not figure out how to do that. When I looked up all I got is this private call

+(void)setAllowsAnyHTTPSCertificate:(BOOL)inAllow forHost:(NSString *)inHost;

Any idea how to do this?

Following is the error I get

The certificate for this server is invalid. You might be connecting to a server that is pretending to be “example.com=0x8b34da0 {NSErrorFailingURLStringKey=https://example.com/test/, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, NSErrorFailingURLKey=https://example.com/test/, NSLocalizedDescription=The certificate for this server is invalid. You might be connecting to a server that is pretending to be “example.com” which could put your confidential information at risk., NSUnderlyingError=0xa26c1c0 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “example.com” which could put your confidential information at risk.", NSURLErrorFailingURLPeerTrustErrorKey=

ios iphone nsurlconnection nsurlconnectiondelegate

share | improve this question | follow |

标签：

举报

9条回答

男人必须洒脱

2楼-- · 2020-06-12 05:30

Try this.

Initiate your session using custom session config as shown below:

let session = URLSession(configuration: URLSessionConfiguration.ephemeral,
                                 delegate: self,
                                 delegateQueue: nil)

Implement the following delegate callback method:

public func urlSession(_: URLSession, task _: URLSessionTask, didReceive challenge: URLAuthenticationChallenge, completionHandler: @escaping (URLSession.AuthChallengeDisposition, URLCredential?) -> Void) {
    guard let serverTrust = challenge.protectionSpace.serverTrust else {
        return completionHandler(URLSession.AuthChallengeDisposition.useCredential, nil)
    }
    return completionHandler(URLSession.AuthChallengeDisposition.useCredential, URLCredential(trust: serverTrust))
}

查看更多

0人赞 添加讨论(0) 举报

•  加载中...

姐就是有狂的资本

3楼-- · 2020-06-12 05:31

In my case, this error occurred due to my firewall blocked the required url. it's worked fine after removing firewall restrictions

查看更多

0人赞 添加讨论(0) 举报

•  加载中...

Lonely孤独者°

4楼-- · 2020-06-12 05:35

In my case, this error occurred due to my system date. It was set as an old date, and the certificate is not effective from that old date. After correct the date, it works.

查看更多

0人赞 添加讨论(0) 举报

•  加载中...

上一页 1 2

登录 后发表回答

相关问题

查看全部

相关文章

• 力软混合式APP快速开发
• java:合并两个排序的链表(递归+非递归)
• XHR 对象实例所有的配置、属性、方法、回调和不可变值
• 交流群招人
• pt-query-digest安装使用及可视化
• Linux下部署Django项目
• pythonic风格代码有什么好处？附12个代码实例
• 解决win8蓝牙脱机方法

查看全部

收藏的人(6)

• 
• 
• 
• 
• 
• 

Answer 1

Try this.

Initiate your session using custom session config as shown below:

let session = URLSession(configuration: URLSessionConfiguration.ephemeral,
                                 delegate: self,
                                 delegateQueue: nil)

Implement the following delegate callback method:

public func urlSession(_: URLSession, task _: URLSessionTask, didReceive challenge: URLAuthenticationChallenge, completionHandler: @escaping (URLSession.AuthChallengeDisposition, URLCredential?) -> Void) {
    guard let serverTrust = challenge.protectionSpace.serverTrust else {
        return completionHandler(URLSession.AuthChallengeDisposition.useCredential, nil)
    }
    return completionHandler(URLSession.AuthChallengeDisposition.useCredential, URLCredential(trust: serverTrust))
}

Answer 2

In my case, this error occurred due to my firewall blocked the required url. it's worked fine after removing firewall restrictions

Answer 3

In my case, this error occurred due to my system date. It was set as an old date, and the certificate is not effective from that old date. After correct the date, it works.