You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.
Wanted to let you know about some oddities seen when running this in AWS, both with and without an ELB sitting in front of it. It is rock solid running in AWS overall, however if you put an ELB in front of your application and try to make it look "pretty" and add SSL, etc it looses its mind. It appears to end up testing the ELB to the application rather than the client to the application.
Thought you might want to add that warning into your docs.
I know you said to avoid SSL, I was just testing it outside the app since I wanted to see what the behaviour looked like.
The text was updated successfully, but these errors were encountered:
Thanks for you issue, that is a great piece of information. As you said, speed testing over SSL is currently giving absurd results. To be honest, it had been giving quite the headache to solve, and still is to fine a solution.
Regarding the ELB situation, i find myself in a similar position when i use my daily docker stack, sitting behind a Traefik balancer. Direct tests are running great, testing through Traefik is awfully slow.
Maybe i'll give it a look some day, but sadly, this project is currently not on my priorities.
e7d
changed the title
Running inside AWS FYI..
Running behind a Load Balancer, with and without SSL
Oct 26, 2020
Wanted to let you know about some oddities seen when running this in AWS, both with and without an ELB sitting in front of it. It is rock solid running in AWS overall, however if you put an ELB in front of your application and try to make it look "pretty" and add SSL, etc it looses its mind. It appears to end up testing the ELB to the application rather than the client to the application.
Thought you might want to add that warning into your docs.
I know you said to avoid SSL, I was just testing it outside the app since I wanted to see what the behaviour looked like.
The text was updated successfully, but these errors were encountered: