A colleague has developed a laravel application which generates a pdf with data from the database.
Local machine: working fine!
Server configured with forge (HTTPS) - using Google Chrome: working fine!
Server configured with forge (HTTP) - using Google Chrome: working fine!
Here is the weird part:
Server configured with forge (HTTP) - using Safari: working fine!
Server configured with forge (HTTPS) - using Safari: it is not working! :(
The download just stops and does not continue.
We already checked the HTTP Header with Postman and everything seems to be in order.
Any pointers on how to handle the https connection using Safari? In some other stackoverflow threads I have read something about that there may be issues regarding the http2 version of the SSL encryption if being used by safari?
The server has been set up by forge and is using the lets encrypt certificate with a test. subdomain.
By stops and does not continue I mean that the safari browser is showing a progress bar which just stops by around a third of the whole progress bar. Does that also answer question 3 and 4?
We tried returning the file from a controller in the following ways:
Both are not working on https in safari.
But they are working on https in chrome.
And also they are working without https in safari.
Any ideas?
When using safari with https there is the following error message on the browser console:
Failed to load resource: The operation couldn’t be completed. Protocol error.
1: there is no difference. We have removed the https2 from the nginx configuration and have restarted the webserver. Same issue.
We also tried to update the header by inserting the following command in the nginx configuration: proxy_hide_header Upgrade; But still no difference after restarting the server.