ueart,luhcsvresi,mohsnd,nihcamyek,tiesbew321,?gifnocecapsbew,hcierebsnoissuksid,k&codluhcs,eegnietsi,?lsd-ni,m&oc,rofttalpluhcs,uhcob-inu-rhur:.con.oi,,?n&-i-g-o-l,aw-ym,e&lletsebgitsnüg,sgnutiel,?i&emtsi,lreb-n&i,yd,??norblieh-sh.ti.&hcraeser-segap,segap,?oitatsksid-ygolonys,pv&-n&i,yd,?nyd,?refeilgitsnüg,?o&c,rp-ytinummoc,?p&h21,iog:ol,,ohsdaerpsym,?r&e&ntrapdeeps.remotsuc,su&-lautriv,lautriv,?t&adpusnd,tub-ni,uor-ym,?vres&-e&bucl,mohym,?bew-emoh:.nyd,,luhcs,??ogiv-&niem,ym,??s&d-&onys,ygolony...

OkHttp is principled and avoids being overly configurable, especially when such configuration is
to workaround a buggy server, test invalid scenarios or that contradict the relevant RFC.
Other HTTP libraries exist that fill that gap allowing extensive customisation including potentially
invalid requests.

Example Limitations

* Does not allow GET with a body.
* Cache is not an interface with alternative implementations.

Get a URL
---------