Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.4.0-RC2
-
Fix Version/s: 1.4.0-RC3
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
By using content-disposition, http://www.ietf.org/rfc/rfc1806.txt, it's possible to provide a name
to the file returned by a get/post request.
Also, while at it, provide a way to return gml+gz as a file (which will require a new delegate I assume).
1. |
KMZ to return good file names as well. | |
|
Brent Owens | |
2. |
PDF could use nice names too. | |
|
Brent Owens |
Thinking about it, I wonder if we might just make a file the default GML-GZIP response. I imagine clients like udig might be able to just ignore it. And if GeoServer is behind a good apache instance than the gzip's already going to be happening. Indeed Paul Ramsey's point has always been that we shouldn't be doing gml-gzip at the geoserver level, since it can be handled at the http protocol level. But this use case would be a bit different, when a person actually wanted the gzipped gml from the browser...