Member Since 3 Years Ago
2,800 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Hi Laracroft, thanks for your reply!
1: there is no difference. We have removed the https2 from the nginx configuration and have restarted the webserver. Same issue.
Here is the http response if it may help:
200 X-Content-Type-Options: nosniff Content-Type: application/pdf Set-Cookie: XSRF-TOKEN=eyJpdiI6ImpVcHZodHkxeDRmL3RJcFdXVk1qTWc9PSIsInZhbHVlIjoiVlNDanBPbVkxeUdhcHR6bGx2THViNFp6Mmw5VEhkR2x1dXMrSFZMTC9ESUdhd1F4VWtxaXRES2RuWEZtZ2pDVDgvSlFmSTgzOExwTGZBTmVQZ3VNTkpHZUhFTHRNZngveEhVbG5UbUdDaDUxN250cDJOWXBaWURXZFhTaHI0VEUiLCJtYWMiOiJjNzIzMTUwMGQ0ZGI4ZDc3Yzk1MGZlZTM0OWNlNGIxOGNjMmU2MWE4ODlhYzgzYzg1NTI1YzcyYTFhNWVlODE4In0%3D; expires=Fri, 30-Oct-2020 14:56:12 GMT; Max-Age=7200; path=/; samesite=lax, test_versservice_session=eyJpdiI6IitkK2wxY0gxd0NoQ1VUT3JjaTdOZHc9PSIsInZhbHVlIjoiSzZkcXRqajcxeFFYWXpFYkhZdks4ZmZrUFJ0Si93TjZ1STJqOHYvL2lqNEVyQzNVR0ZPYzFVbTVaOGdNRW4wend3R251cHlmWmxCOTBNNjNUdUlvaGNjTG5kWVYrc1VBZ2g3dnhRYXA4eC9KS1V0ZnFHQzZVR0p1YSt5MXVLUlgiLCJtYWMiOiIwODYyNmYyZWQzYWI4MTE3MmNmMDNiNjg4NTU1NzIzYTBhZGYwYzc3MGZhZWUzZjlmNjgyODRlOWY5NjE2ZDc2In0%3D; expires=Fri, 30-Oct-2020 14:56:12 GMT; Max-Age=7200; path=/; httponly; samesite=lax Date: Fri, 30 Oct 2020 12:56:12 GMT X-Frame-Options: SAMEORIGIN Content-Disposition: inline; filename=11604062572-maklervertrag.pdf X-XSS-Protection: 1; mode=block Content-Length: 18836 Cache-Control: no-cache, private Server: nginx
Hi @laracoft thanks for your quick reply!
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:
return response()->download(storage_path() . $file->name);
return response()->file(storage_path() . $file->name);
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.
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.
Could it be related to the follwing issue? https://stackoverflow.com/questions/37762163/safari-fails-to-give-response-when-using-http-2
Started a new Conversation Safari SSL / HTTP2 - File Download Not Working
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.