What do you guys think about limiting the https certificate errors to one per page request, and not one per each item within the page request. Hopefully that makes sense. The issue is when you go to a site like [0] and don't have the issuing cert installed, in this case Valicert and GoDaddy, you get bombarded with tons of dialogs asking you to continue or cancel. I've tried to come up with a way myself, without much luck. Any ideas? [0] https://https.openbsd.org/cgi-bin/order -- James Turner BSD Group Consulting http://www.bsdgroup.org
* James Turner <james@bsdgroup.org> [081024 17:43]:
What do you guys think about limiting the https certificate errors to one per page request, and not one per each item within the page request. Hopefully that makes sense. The issue is when you go to a site like [0] and don't have the issuing cert installed, in this case Valicert and GoDaddy, you get bombarded with tons of dialogs asking you to continue or cancel. I've tried to come up with a way myself, without much luck. Any ideas?
That's because currently each https url gets forwarded to the https dpi which is stateless. It is on my list to turn this into some kind of cert state holding module (at least in memory, maybe similar to the basic auth one). Until then there is not much you can do (besides writing a patch yourself, which you are most welcome to do)! Hope this clears things up a bit, Christian -- You may use my gpg key for replies: pub 1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)
participants (2)
-
Christian.Kellermann@nefkom.net
-
james@bsdgroup.org