5 ms·

Not every web service is easy to set up with HTTPS as a simple Let's Encrypt service. Take a game. It dynamically balances between servers rented and destroyed

Not every web service is easy to set up with HTTPS as a simple Let's Encrypt service. Take a game. It dynamically balances between servers rented and destroyed on the fly. It needs a wildcard DNS certificate. Then all the sub-servers need to have that wildcard certificate. In conclusion, deprecating HTTP makes it harder for people to get started on the web. How are you going to get certificates for IP address' control dashboard, after all?

wccrawford 6y ago
A game absolutely should be use HTTPS anyhow, for their own security. But I'd say that anyone that has an operation so big that it dynamically creates and destroys servers to balance load should probably already be paying for their own wildcard cert anyhow.
- crazypython 6y ago
  > A game absolutely should be use HTTPS anyhow, for their own security. The game has no log-in or sign-up; no account system. The only potentially sensitive data sent is the nickname the user enters. > But I'd say that anyone that has an operation so big that it dynamically creates and destroys servers to balance load should probably already be paying for their own wildcard cert anyhow. The game is free and ad-supported. Dynamically creating and destroying servers is a basic requirement.
imtringued 6y ago
>It needs a wildcard DNS certificate. Then all the sub-servers need to have that wildcard certificate. Just give each server a separate domain and certificate as you create them. The matchmaking algorithm returns a url pointing to the server. >How are you going to get certificates for IP address' control dashboard, after all? By clicking the damn button?
- crazypython 6y ago
  > Just give each server a separate domain and certificate as you create them. The matchmaking algorithm returns a url pointing to the server. Do you mean a separate subdomain? (A separate domain would be very expensive.) I would need to figure out how to generate and provision certificates, in that case.
conradfr 6y ago
Similarly I got stung by Chrome recently. I have a side project that plays webradio streams. A lot of them don't have https, some links even are ip addresses and Chrome won't allow to request them on my https site. In the end it forced me to create a stream proxy that I have to host...

wccrawford 6y ago

A game absolutely should be use HTTPS anyhow, for their own security. But I'd say that anyone that has an operation so big that it dynamically creates and destroys servers to balance load should probably already be paying for their own wildcard cert anyhow.

crazypython 6y ago
> A game absolutely should be use HTTPS anyhow, for their own security. The game has no log-in or sign-up; no account system. The only potentially sensitive data sent is the nickname the user enters. > But I'd say that anyone that has an operation so big that it dynamically creates and destroys servers to balance load should probably already be paying for their own wildcard cert anyhow. The game is free and ad-supported. Dynamically creating and destroying servers is a basic requirement.

imtringued 6y ago

>It needs a wildcard DNS certificate. Then all the sub-servers need to have that wildcard certificate. Just give each server a separate domain and certificate as you create them. The matchmaking algorithm returns a url pointing to the server. >How are you going to get certificates for IP address' control dashboard, after all? By clicking the damn button?

crazypython 6y ago
> Just give each server a separate domain and certificate as you create them. The matchmaking algorithm returns a url pointing to the server. Do you mean a separate subdomain? (A separate domain would be very expensive.) I would need to figure out how to generate and provision certificates, in that case.

conradfr 6y ago

Similarly I got stung by Chrome recently. I have a side project that plays webradio streams. A lot of them don't have https, some links even are ip addresses and Chrome won't allow to request them on my https site. In the end it forced me to create a stream proxy that I have to host...