Welcome! Log In Create A New Profile

Advanced

[PATCH] Clarify 495 response message

Georg Pfuetzenreuter via nginx-devel
April 28, 2022 07:40AM
Hello!

The current message "The SSL certificate error" feels cut off and is
ambiguous.
I suggest the following change, which clarifies the 495 response whilst
keeping it flexible enough to be used for different client certificate
errors.

Best,
Georg

# HG changeset patch
# User Georg Pfuetzenreuter <mail@georg-pfuetzenreuter.net>
# Date 1651145208 -7200
# Thu Apr 28 13:26:48 2022 +0200
# Node ID 9c2491a6c4615647768a13280eaa1e22b20fc36d
# Parent a736a7a613ea6e182ff86fbadcb98bb0f8891c0b
Clarify 495 response

Adjust HTTP 495 response message shown to an end user to make more sense.

diff -r a736a7a613ea -r 9c2491a6c461 src/http/ngx_http_special_response.c
--- a/src/http/ngx_http_special_response.c Tue Feb 08 17:35:27 2022
+0300
+++ b/src/http/ngx_http_special_response.c Thu Apr 28 13:26:48 2022
+0200
@@ -253,11 +253,11 @@

static char ngx_http_error_495_page[] =
"<html>" CRLF
-"<head><title>400 The SSL certificate error</title></head>"
+"<head><title>400 SSL client certificate error</title></head>"
CRLF
"<body>" CRLF
"<center><h1>400 Bad Request</h1></center>" CRLF
-"<center>The SSL certificate error</center>" CRLF
+"<center>SSL client certificate error</center>" CRLF
;
_______________________________________________
nginx-devel mailing list -- nginx-devel@nginx.org
To unsubscribe send an email to nginx-devel-leave@nginx.org
Subject Author Views Posted

[PATCH] Clarify 495 response message

Georg Pfuetzenreuter via nginx-devel 385 April 28, 2022 07:40AM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 124
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready