cURL SSL PUT / POST(php)(NSS与OpenSSL)的延迟响应 [英] Delayed responses for cURL SSL PUTs/POSTs (php) (NSS vs OpenSSL)

查看:333
本文介绍了cURL SSL PUT / POST(php)(NSS与OpenSSL)的延迟响应的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有两个基于Fedora的apache网络服务器使用php / cURL进行相同的SSL PUT / POST调用。一个工作正常,但与另一个呼叫成功,但需要一个非常长的时间来返回响应(〜10分钟)。 (GETs似乎不受影响)

I have two Fedora-based apache webservers making the same SSL PUT/POST calls with php/cURL. One works fine, but with the other the call succeeds but takes a VERY long time to return a response (~10 min). (GETs don't seem affected)

工作服务器的cURL使用OpenSSL进行SSL,而非工作版本使用更高版本的cURL,使用NSS进行SSL

The working server's cURL uses OpenSSL for SSL, while the non-working version uses a later version of cURL that uses NSS for SSL

我对SSL实现或对cURL的影响一无所知。什么会导致SSL PUT / POST响应中的这种显着延迟?

I know nothing about SSL implementations or their effect on cURL. What would cause such a significant delay in SSL PUT/POST responses?

任何建议感谢 - 感谢 -

Any suggestions appreciated- Thanks--

推荐答案

您在httpd.conf中检查了KeepAlive选项,它应该为On。
请参阅 http://www.debian-administration.org/articles/188

Have you check your KeepAlive options in httpd.conf, it should be On. Please refer to http://www.debian-administration.org/articles/188

这篇关于cURL SSL PUT / POST(php)(NSS与OpenSSL)的延迟响应的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆