Void Mysterious Posted April 8, 2020 Share Posted April 8, 2020 Hello, Im getting HTTP error 499 in my script when using llHTTPRequest. This happens when the server im making the requests to only accepts HTTPS, if its HTTP it works fine. Anyone encountered this? Thanks! Link to comment Share on other sites More sharing options...
Lucia Nightfire Posted April 8, 2020 Share Posted April 8, 2020 I "think" this was brought up yestreday at the server UG: Idk if the solution is needed for external servers to accept https-in from LL servers or if it's only for LL servers to accept https-in from external servers or both. Link to comment Share on other sites More sharing options...
Lindens Oz Linden Posted April 8, 2020 Lindens Share Posted April 8, 2020 5 hours ago, Matu said: Im getting HTTP error 499 in my script when using llHTTPRequest. This happens when the server im making the requests to only accepts HTTPS, if its HTTP it works fine. That usually means that the remote server is not reachable (not responding). Check to see whether the server is receiving your request. Link to comment Share on other sites More sharing options...
Void Mysterious Posted April 9, 2020 Author Share Posted April 9, 2020 15 hours ago, Oz Linden said: That usually means that the remote server is not reachable (not responding). Check to see whether the server is receiving your request. Hello Oz, Yes, the server is reachable, when i force all traffic to use HTTPS it fails, if i allow HTTP it works fine. Thank you. Link to comment Share on other sites More sharing options...
Lindens Oz Linden Posted April 9, 2020 Lindens Share Posted April 9, 2020 10 hours ago, Matu said: Yes, the server is reachable, when i force all traffic to use HTTPS it fails, if i allow HTTP it works fine. Not sure I understand what you're saying there ... it is not true that if the server responds to http that it will always respond to https. Have you looked at the server logs to see that it is getting the request and thinks it's responding? Link to comment Share on other sites More sharing options...
Void Mysterious Posted April 10, 2020 Author Share Posted April 10, 2020 On 4/9/2020 at 11:52 AM, Oz Linden said: Not sure I understand what you're saying there ... it is not true that if the server responds to http that it will always respond to https. Have you looked at the server logs to see that it is getting the request and thinks it's responding? Let me try to explain with a bit more of detail. If i set my webserver to accept only HTTPS by changing the virtualhost using: RewriteEngine on RewriteCond %{SERVER_NAME} =(DOMAIN REMOVED) [OR] RewriteCond %{SERVER_NAME} =(DOMAIN REMOVED) RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] then the lsl scripts fails with error 499. From the logs i see this With the virtuahost modification Without the virtualhost modification Link to comment Share on other sites More sharing options...
Lindens Oz Linden Posted April 13, 2020 Lindens Share Posted April 13, 2020 What you did was create a redirect. There's a much simpler way to do that; see the documentation for the RedirectSSL directive. If your request was a GET (you didn't say), your request might have worked (your redirect did not include any query string), but it won't work for any other method; see the wiki: Quote While the HTTP status code from the server is provided to the script, redirect codes such as 302 will result in the redirect being automatically and transparently followed ONLY IF the HTTP_METHOD is GET It's also possible that the redirect you created was not to a valid url; impossible to say without specific detail or a complete log. Link to comment Share on other sites More sharing options...
Void Mysterious Posted April 15, 2020 Author Share Posted April 15, 2020 On 4/13/2020 at 11:58 AM, Oz Linden said: What you did was create a redirect. There's a much simpler way to do that; see the documentation for the RedirectSSL directive. If your request was a GET (you didn't say), your request might have worked (your redirect did not include any query string), but it won't work for any other method; see the wiki: It's also possible that the redirect you created was not to a valid url; impossible to say without specific detail or a complete log. Thanks for the reply. I kind of figured it out. When using the URL https://www.example.com (Not the real domain) it fails, however if i use https://example.com it works fine, so i guess its some configuration issue on the webserver. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please take a moment to consider if this thread is worth bumping.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now