Same. My home Unifi network is all integrated with PiHole and does DNS over HTTPS to CF. Having the 1.1.1.1 on my phone is great except when I'm at home and want it disabled.
Why do you think HTTPS would fix this? For the TLS case, there are enough MITM proxies, both in the Enterprise and elsewhere, to make this a real concern. There are also API Aggrigators which are effectively MITM and…
The "?api-version" approach in the doc is there for exactly the reason you call out. Azure uses this approach. By omitting "/v1.0" from the path it makes the actual URL's far more durable, as they're not version…
There's nothing wrong with RPC APIs. Other than being "Not Cool" due to the legacy of SOAP, they can deliver some very nice value. Various RPC mechanisms like Bond and Protocol Buffers (and more recently GRPC) are…
There are a number of examples to cite showing what you say isn't true. Allowing totally arbitrary OData $filter expressions does lead to problems, but recent versions of OData have a nice mechanism to describe (and…
Delta queries are pretty easy, assuming you have a rich data store behind your data. As others have said, your data store needs to be able to say, "Show me changes since XYZ". Most of the Big Apps can do that, and from…
It turns out that uploading files is hard. Files come in a variety of sizes, networks sometimes don't work, browser processes come-and-go, some users expect restart semantics, some don't...
The API version header has a few problems. 1. Older proxies used to remove/strip headers they don't understand. 2. Frameworks and libraries don't always give access to n non-standard headers, meaning they just can't…
Same. My home Unifi network is all integrated with PiHole and does DNS over HTTPS to CF. Having the 1.1.1.1 on my phone is great except when I'm at home and want it disabled.
Why do you think HTTPS would fix this? For the TLS case, there are enough MITM proxies, both in the Enterprise and elsewhere, to make this a real concern. There are also API Aggrigators which are effectively MITM and…
The "?api-version" approach in the doc is there for exactly the reason you call out. Azure uses this approach. By omitting "/v1.0" from the path it makes the actual URL's far more durable, as they're not version…
There's nothing wrong with RPC APIs. Other than being "Not Cool" due to the legacy of SOAP, they can deliver some very nice value. Various RPC mechanisms like Bond and Protocol Buffers (and more recently GRPC) are…
There are a number of examples to cite showing what you say isn't true. Allowing totally arbitrary OData $filter expressions does lead to problems, but recent versions of OData have a nice mechanism to describe (and…
Delta queries are pretty easy, assuming you have a rich data store behind your data. As others have said, your data store needs to be able to say, "Show me changes since XYZ". Most of the Big Apps can do that, and from…
It turns out that uploading files is hard. Files come in a variety of sizes, networks sometimes don't work, browser processes come-and-go, some users expect restart semantics, some don't...
The API version header has a few problems. 1. Older proxies used to remove/strip headers they don't understand. 2. Frameworks and libraries don't always give access to n non-standard headers, meaning they just can't…