22 ms·
If you control both the client and the server you can have quite long URLs. I don't agree that a long URLs necessarily indicates a broken design. I've done it
by martinced 14y ago
If you control both the client and the server you can have quite long URLs.
I don't agree that a long URLs necessarily indicates a broken design. I've done it and configure my web server (Tomcat) to accept longer GET requests (so +1 to 'asiermarques' here, who pointed out that it depends on how the web server is configured too).
There are services out there, like Google Charts if I'm not mistaken (but I may be mistaking it with something else) which, by the way they work, forces you to create quite long URLs. It generates a graph on the fly and nothing is modified on the server, so a GET is used, not a POST (which, IMHO, makes sense).
From the thread I seem to understand that the Data URI scheme implies that company should start to upgrade or replace their broken load balancer that "mysteriously" truncate URLs and cause all manner of weird bugs ; )
- danielweber 14y agoIf you control both the client and the server . . . and all proxies that may be in-between. I've debugged more than one client issue where people were doing something really weird over port 80.
- Dylan16807 14y agoThe thing is, if you put raw data in a URL it's no longer really a URL. If you're transforming data it makes sense to put the data somewhere else, and somewhere else means POST. Even if the data doesn't get stored permanently. REST never really considered requests that don't involve resources..