Closed studytnot closed 10 years ago
I don't think that most web servers autodetect SSL/TLS and plain HTTP. One shprx only handles only SSL/TLS or only plain HTTP, not both. Why not run 2 shrpx process for each of them? Are you suggesting a feature to share a configuration, something like "include" feature of nginx?
why can't most web servers autodetect SSL/TLS and plain HTTP ? will this make the code more complicated ? i'm not suggesting the "include" feature. because the shrpx configuration is not so complicated now.
I said that because apache is not capable to do this.
Technically, you can guess the incoming data is SSL/TLS handshake or plain HTTP request, but it is still a guess. Also it certainly makes code complex. In shrpx, we rely on the fact that it is configured either SSL/TLS or plain HTTP. We don't see the merit to invest the time and energy for this complexity. This is probably WONTFIX.
thank you so much
i know shrpx can process notls data with --no-tls option, and can process tls data without the option. so my question is why i need the --no-tls flag? can shrpx judge whether the request is tls or no-tls at the run time ? can shrpx process tls and notls request in one process with the same configuration?