Nginx 1.15.6 with openssl 1.1.1 , EarlyData not sent
We have set " ssl_early_data on; " and "proxy_set_header Early-Data $ssl_early_data ;" in nginx 1.15.6 config built with openssl 1.1.1 but when we are running the below command , it is showing EarlyData is not Sent. any idea how to resolve this issue?
openssl s_client -connect www.rupeevest.com:443
SSL handshake has read 4693 bytes and written 399 bytes
Verification: OK
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 2048 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
nginx openssl tls1.3
add a comment |
We have set " ssl_early_data on; " and "proxy_set_header Early-Data $ssl_early_data ;" in nginx 1.15.6 config built with openssl 1.1.1 but when we are running the below command , it is showing EarlyData is not Sent. any idea how to resolve this issue?
openssl s_client -connect www.rupeevest.com:443
SSL handshake has read 4693 bytes and written 399 bytes
Verification: OK
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 2048 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
nginx openssl tls1.3
add a comment |
We have set " ssl_early_data on; " and "proxy_set_header Early-Data $ssl_early_data ;" in nginx 1.15.6 config built with openssl 1.1.1 but when we are running the below command , it is showing EarlyData is not Sent. any idea how to resolve this issue?
openssl s_client -connect www.rupeevest.com:443
SSL handshake has read 4693 bytes and written 399 bytes
Verification: OK
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 2048 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
nginx openssl tls1.3
We have set " ssl_early_data on; " and "proxy_set_header Early-Data $ssl_early_data ;" in nginx 1.15.6 config built with openssl 1.1.1 but when we are running the below command , it is showing EarlyData is not Sent. any idea how to resolve this issue?
openssl s_client -connect www.rupeevest.com:443
SSL handshake has read 4693 bytes and written 399 bytes
Verification: OK
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 2048 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
nginx openssl tls1.3
nginx openssl tls1.3
asked Nov 17 '18 at 11:25
Rahul MistryRahul Mistry
13
13
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
In order to send "early-data", client and server must support PSK exchange mode. See https://tools.ietf.org/html/rfc8446#section-2.3
To verify using OpenSSL, as an use-case example, first save the session to a file, next use that session file and send early data to server. Note your server should support TLS 1.3
$> openssl s_client -connect www.yourhostedserver.com:443 -tls1_3 -sess_out /path-to-session-file/session.pem
$> openssl s_client -connect www.yourhostedserver.com:443 -tls1_3 -sess_in /path-to-session-file/session.pem -early_data /path-to-early-data-file/early-data.txt
//early-data.txt file contains a text like
GET /HTTP/1.1
Hope this helps!
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53350763%2fnginx-1-15-6-with-openssl-1-1-1-earlydata-not-sent%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In order to send "early-data", client and server must support PSK exchange mode. See https://tools.ietf.org/html/rfc8446#section-2.3
To verify using OpenSSL, as an use-case example, first save the session to a file, next use that session file and send early data to server. Note your server should support TLS 1.3
$> openssl s_client -connect www.yourhostedserver.com:443 -tls1_3 -sess_out /path-to-session-file/session.pem
$> openssl s_client -connect www.yourhostedserver.com:443 -tls1_3 -sess_in /path-to-session-file/session.pem -early_data /path-to-early-data-file/early-data.txt
//early-data.txt file contains a text like
GET /HTTP/1.1
Hope this helps!
add a comment |
In order to send "early-data", client and server must support PSK exchange mode. See https://tools.ietf.org/html/rfc8446#section-2.3
To verify using OpenSSL, as an use-case example, first save the session to a file, next use that session file and send early data to server. Note your server should support TLS 1.3
$> openssl s_client -connect www.yourhostedserver.com:443 -tls1_3 -sess_out /path-to-session-file/session.pem
$> openssl s_client -connect www.yourhostedserver.com:443 -tls1_3 -sess_in /path-to-session-file/session.pem -early_data /path-to-early-data-file/early-data.txt
//early-data.txt file contains a text like
GET /HTTP/1.1
Hope this helps!
add a comment |
In order to send "early-data", client and server must support PSK exchange mode. See https://tools.ietf.org/html/rfc8446#section-2.3
To verify using OpenSSL, as an use-case example, first save the session to a file, next use that session file and send early data to server. Note your server should support TLS 1.3
$> openssl s_client -connect www.yourhostedserver.com:443 -tls1_3 -sess_out /path-to-session-file/session.pem
$> openssl s_client -connect www.yourhostedserver.com:443 -tls1_3 -sess_in /path-to-session-file/session.pem -early_data /path-to-early-data-file/early-data.txt
//early-data.txt file contains a text like
GET /HTTP/1.1
Hope this helps!
In order to send "early-data", client and server must support PSK exchange mode. See https://tools.ietf.org/html/rfc8446#section-2.3
To verify using OpenSSL, as an use-case example, first save the session to a file, next use that session file and send early data to server. Note your server should support TLS 1.3
$> openssl s_client -connect www.yourhostedserver.com:443 -tls1_3 -sess_out /path-to-session-file/session.pem
$> openssl s_client -connect www.yourhostedserver.com:443 -tls1_3 -sess_in /path-to-session-file/session.pem -early_data /path-to-early-data-file/early-data.txt
//early-data.txt file contains a text like
GET /HTTP/1.1
Hope this helps!
answered Jan 14 at 6:28
naga headhunternaga headhunter
73110
73110
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53350763%2fnginx-1-15-6-with-openssl-1-1-1-earlydata-not-sent%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown