-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
httpS server seems to not work in v1.14 #4831
Comments
SSL_ERROR_RX_RECORD_TOO_LONG this usually happen if you try to connect to an https on a server that is http. |
@omerbrandis , does the comment from @micheleselea explain the failure that you reported. |
Hello matejk & micheleselea as i've mentioned before, i did not change my code/configuration, only the linkage to v1.14.
:-) |
Thank you, @omerbrandis. Can you provide a sample code that demonstrates the problem? |
Hello Matejk, I've tried to reproduce the error using simpler code , i've taken the example provided at https://pocoproject.org/ (made the changes required for serving over ssl), the error did not reproduce. i've then taken the next step, it seems the error is in method HTTPServerResponse::sendFile, I'm not really sure how to debug this further.... |
I'm pretty sure it's the changes to HTTPServerResponseImple.cpp in commit 710c2a4. I don't think you can use sendFile with a TLS connection. I reverted just that file and HTTPServerResponse::sendFile is working again as expected for me over a TLS connection. |
FWIW: our index.html (1353 bytes) was able to get served correctly but our favicon.ico (3902 bytes) would trigger the record too long error. |
Hm, |
mmm I don't get it, I usually use |
upgraded my existing application to use poco 1.14 with openssl 3.0.15
when using firefox to get a page from the server over ssl it shows a "SSL_ERROR_RX_RECORD_TOO_LONG" error.
chorme did not show an error msg, but was unable to render, it looks like it kept retrying to get the page.
when using poco 1.13.3 application works.
The text was updated successfully, but these errors were encountered: