Hello,
I am coming back to the subject because I have setup a server setting only its SslConfiguration (I did not wanted to listen to non ssl connection).
What I have noticed some days ago are some "strange entries" in the server's logs. I initially thought it was some packets forward trials on the server's port but in fact, it looks like if the server was listening to any port in range 808x not already used by any other server (I could be wrong reason why I am asking you).
Referring to that post, the default port was 80 (already in use so perhaps it could have moved to 808x ?)
For example, my server is listening for SSL connection on port 51049. In the logs, I can see
But when I point my browser to [server's IP]:8080, I am creating a log entry with my own IP
And it logs the same if I am pointing to 8081, 808x etc.
Is there something I did not understood ? Perhaps the fact I did not setup the "non SSL port" to listen to ?
Many thanks
I am coming back to the subject because I have setup a server setting only its SslConfiguration (I did not wanted to listen to non ssl connection).
What I have noticed some days ago are some "strange entries" in the server's logs. I initially thought it was some packets forward trials on the server's port but in fact, it looks like if the server was listening to any port in range 808x not already used by any other server (I could be wrong reason why I am asking you).
Referring to that post, the default port was 80 (already in use so perhaps it could have moved to 808x ?)
For example, my server is listening for SSL connection on port 51049. In the logs, I can see
But when I point my browser to [server's IP]:8080, I am creating a log entry with my own IP
And it logs the same if I am pointing to 8081, 808x etc.
Is there something I did not understood ? Perhaps the fact I did not setup the "non SSL port" to listen to ?
Many thanks
Last edited:
