New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WFS 2.0 wrong extension response to a spatialite zip request #4933
Comments
the FILENAME key is used to create the OGR datasource, so it should probably be set to result.db instead of result.db.zip. However when using zipped form, we should probably append ".zip" to the filename of the Content-Disposition header. cc @rouault |
@tbonfort I will take after this bug. My intent is, when FORM=zip, to analyse the filename. If it is of the kind foo.bar.zip, then the OGR datasource will be created with foo.bar as a name, and the result will be zipped in foo.bar.zip. If FILENAME is not specified or just as foo.zip then the OGR datasource will be named result.dat. |
…xt.zip", use basename.ext as the name of the OGR datasource (#4933)
I believe that this one can be closed like the referenced #4856. |
Mapserver use wrong extension in a response to a spatialite zipped request.
Starting from this setting:
OUTPUTFORMAT
NAME "SPATIALITE"
DRIVER "OGR/SQLITE"
MIMETYPE "application/zip"
FORMATOPTION "DSCO:SPATIALITE=YES"
FORMATOPTION "STORAGE=memory"
FORMATOPTION "FORM=zip"
FORMATOPTION "FILENAME=result.db.zip"
END
The zip resulted will not contain a file .sqlite but instead a file with zip extension.
But this is not a zip file.It is instead a real spatialite db. The MapServer has named its extension .zip instead of .sqlite
The text was updated successfully, but these errors were encountered: