If not, the level of debug output may help you pinpoint the problem more so than wget's debug output would. If so, then something is wonky with wget and you might want to re-build or reinstall it. Wget allows you to install a global startup file (/usr/local/etc/wgetrc by default) for site settings. Lastly, try using OpenSSL in s_client mode: openssl s_client -cert cert.pem -key req.pem -connect host:port -debugĪnd see if things work at that level. take the https form of the request (data doesnt change, but metadata requests need URL encoding - see metadata page). wget and curl are used to put a request directly on the command line. If you've already done that, perhaps you can try from another machine to ensure that it's not something strange with the version of OpenSSL you're using. WGET and CURL - Direct command line tools. I would suggest taking your certificate and key, combining it into PKCS12 (or just importing it as PEM if your browser supports the format) and ensuring that everything is working on that front first. I am using nginx you don't mention what you're using, so I'm not sure if Apache would return the same responses. providing a valid cert that the server does not like: 403 forbidden.If so, then something is wonky with wget and you might want to re-build or reinstall it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |