On 09/02/16 08:14, Robert Coup wrote: > fyi, the "X-" prefix for custom headers is not the recommended approach any > more... http://tools.ietf.org/html/rfc6648#section-3 > *Recommendations for Creators of New Parameters* > Creators of new parameters to be used in the context of >> application protocols: >> 1. SHOULD assume that all parameters they create might >> become standardized, public, commonly deployed, or usable across multiple >> implementations. >> 2. SHOULD employ meaningful parameter names that they have reason >> to believe are currently unused. >> 3. SHOULD NOT prefix their parameter names with "X-" or >> similar constructs. > Rob :)
Thanks for the link, Rob. That is a good point. I felt that custom headers are a bad idea and was soliciting suggestions for best-practices for RESTful directory traversal with HEAD to find a parent. Surely someone has tried this? Or is it an acceptable practice to assume that HTTP URLs can be parsed to remove trailing path elements? Kind regards, -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
