So I guess "application/xpl+xml" would be the better choice as well?
My understanding multiple extensions in use but same mimetype of "xproc+xml". As with
xq=application/xquery xqm=application/xquery xquery=application/xquery xqy=application/xquery
Although I note the list has:
xsl=text/xml xslt=application/xslt+xml
On 9 June 2017 at 11:49, Christian Grün christian.gruen@gmail.com wrote:
Is there some reason not to go with "application/xproc+xml"? [1]
Should be fine. So I guess "application/xpl+xml" would be the better choice as well?
And it looks like BaseX will treat it as XML [2]
Exactly ;)
[1]
https://www.w3.org/XML/XProc/docs/langspec.html#media-type-registration
[2]
https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/ba...
On 9 June 2017 at 11:01, Christian Grün christian.gruen@gmail.com
wrote:
Hi Andy,
Adding the extensions statically is surely the least effort for now.
I can add the following two mappings:
xpl=application/xml xproc=application/xml
Are some more that I should include?
Thanks, Christian
On Fri, Jun 9, 2017 at 11:49 AM, Andy Bunce bunce.andy@gmail.com
wrote:
Hi,
I notice that fetch:content-type()[1] returns
"application/octet-stream"
for files with the commonly used XProc file extensions *.xpl and *.xproc. This seems to be driven from the list in src/main/resources/media-types.properties [2] Would it be possible to add these extensions as
"application/xproc+xml"
or add a mechanism to allow extension/customisation? Maybe similar to
[3]
For static files served from jetty adding mime-mapping elements to web.xml works [4]
/Andy
[1] http://docs.basex.org/wiki/Fetch_Module#fetch:content-type [2]
https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/resources/m...
[3]
http://docs.oracle.com/javase/7/docs/api/javax/activation/MimetypesFileTypeM...
[4]
https://stackoverflow.com/questions/33803109/how-can-i-set-mime-mapping-to-a...