My point about URL length with GET. This is not about what's possible but
what's practical given the various network topologies out-in-the-wild. An
sample use case... There's an federal bureau that utilize web-application
firewalls (WAF) across their topology. There's a URL length restriction where
anything beyond that length automatically gets rejected with a HTTP 404
(conveniently, no other explanations). The length of this URL is approaching
that limit. You do not want to be debugging issues for users with this kinda
of topology, it's a rabbit-hole.
> On Jul 1, 2012, at 5:56 PM, Jeff McWhirter wrote:
>
> http://ramadda.org/repository/entry/show/gfs80.gif?idv.action=action.makeimage&width=650&levels0=3&height=400&c_int0=5.0&mapcolor=ff0000×0=0&c_b0=0.0&s_p0=top¶m=Temperature&ct0=Blues&c_w0=1&f_sk0=0&wireframe=true&latlon.visible=true&proj=US%3ECONUS&submit=Make+Image&r_mx0=45.0&output=idv.grid&mapwidth=2&c_mx0=45.0&unit0=celsius&dsp0=planviewcolor&product=product.image&f_d0=1&maps=%2Fauxdata%2Fmaps%2FOUTLUSAM&entryid=b835f612-5975-468f-86af-16e1a8e25219&r_mn0=-90.0&dll0=hello&backgroundimage=fixed-bluemarble&f_s0=4&zoom=0.7&c_mn0=-90.0&c_l0=true&bg=ffffff&latlon.spacing=30
Tom Kunicki
Center for Integrated Data Analytics
U.S. Geological Survey
8505 Research Way
Middleton, WI 53562