4 ms·
People have their reasons, we respect that. But a default to https, why not? It seems reasonable to me. I am not sure on how to get https:// https:// by defaul
by cryptoplot 8y ago
People have their reasons, we respect that. But a default to https, why not? It seems reasonable to me.
I am not sure on how to get https:// https:// by default while still supporting http:// http:// for people who prefer it. It may take some advanced 302 redirect.
We will investigate and see what we can do there. Suggestions are much appreciated.
- gregmac 8y agoI'm still very unclear on a legitimate use case for this, and personally wouldn't do it until I had a good reason. That said, a couple ideas on how to implement: * Use an alternate domain, eg `insecure.domain.com` * Use an alternate path prefix, eg `domain.com/insecure/` -- your app would have to be able to handle this * Use a parameter that sets a cookie that your load balancer/reverse proxy can understand, eg, `http://domain.com/?https=false` http://domain.com/?https=false`, and will prevent redirect -- definitely the most complex from the proxy point-of-view, but means the URL (other than the scheme) is consistent for both types of user
- exoesquitur 8y agoI sometimes parse web data with uC based devices that are not capable of doing https with the memory space available. I appreciate the ability to use http when I need to.
- exoesquitur 8y agoI use http from embedded devices that cannot do https due to memory constraints. Http access is appreciated for this use case. But.... Do you guys have a business model that is going to keep you around long enough for me to bother hardcoding your api into embedded devices? I build things that connect real world actions to cryptocurrency markets, diverting power, metering resource consumption, etc.
- cryptoplot 8y agoPlease get in touch by email if you need something more than the free API. For your embedded devices, we can make something special just for you