Answer the question
In order to leave comments, you need to log in
What is the overhead of https vs http traffic?
Good time. I am developing a Rest API for one service, and transferred it to https. It seems like the traffic will be hidden, all passwords, if they are, will not be lost along the way. But programmers who write applications for mobile devices (iOS and Android) said they would not switch, because "https connection, due to the constant 'handshake' on each connection, has a huge traffic overhead" compared to a regular http connection.
How fair is this? Is the overhead really that big for mobile traffic.
+ The server admin also stated that when using https, the load on the server network is much higher.
Is there any research on this issue, and what is the common practice when working with APIs over mobile?
Thank you!
Answer the question
In order to leave comments, you need to log in
In IT, when some specialist says something, you can just ask him for a link to tests and metrics
. I advise you to ask them for the same tests and metrics
. Maybe they will help get rid of unqualified staff
stackoverflow.com/a/149445
stackoverflow. com/questions/1468648/https-vs-http-...
https://www.keycdn.com/blog/https-performance-overhead/
Traffic overhead 5kb per connection
CPU overhead 2%
The counter() function is this thing
. Nothing is hardcoded in it, the variable is currentCount
captured from the outside, using a closure .
And the increment operator ( ++
) increases it every time.
makeCounter was called 1 time, which means the variable was declared only 1 time, and then it was incremented 3 times, but not called
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question