From: Stefan H. <hel...@gm...> - 2014-09-08 12:25:45
|
Hi everybody, I start yaws in embedded mode (inside a supervisor tree, as described on http://yaws.hyber.org/embed.yaws). For served files that does not have any file name extension (such as http://<host>/example) the default content type seems to be set to "text/plain". Is there some information anywhere on how I can configure the content type field for static files to be any content type that I like (for instance "text/html")? I see in the documentation (for instance http://yaws.hyber.org/internals.yaws) that one can set the #mime_types_info record of the sconf to override the default config in an appmod but I do not see any specifics on how to do this or how I would do this for the case where there is no file name extension. Any help, or pointers to examples, on how to do this would be much appreciated. /Stefan |
From: Steve V. <vi...@ie...> - 2014-09-08 13:23:29
|
On Mon, Sep 8, 2014 at 8:25 AM, Stefan Hellkvist <hel...@gm...> wrote: > Hi everybody, > > I start yaws in embedded mode (inside a supervisor tree, as described on > http://yaws.hyber.org/embed.yaws). For served files that does not have > any file name extension (such as http://<host>/example) the default > content type seems to be set to "text/plain". > > Is there some information anywhere on how I can configure the content type > field for static files to be any content type that I like (for instance > "text/html")? > > I see in the documentation (for instance > http://yaws.hyber.org/internals.yaws) that one can set the > #mime_types_info record of the sconf to override the default config in an > appmod but I do not see any specifics on how to do this or how I would do > this for the case where there is no file name extension. Any help, or > pointers to examples, on how to do this would be much appreciated. > If you pass a server config list to yaws_api:embedded_start_conf, you can set the default mime type like this: yaws_api:embedded_start_conf(DocRoot, [{mime_types_info, [{default_type,"application/foo"}]}]) Replace "application/foo" with whatever you want the default mime type to be for your server. Note that the second argument can also be a list of lists for the case of multiple virtual servers, in which case you have to set the mime_types_info element into each of the appropriate server list(s) for your system. --steve |
From: Stefan H. <hel...@gm...> - 2014-09-08 14:14:07
|
That worked splendidly! Thanks! /Stefan On Mon, Sep 8, 2014 at 3:23 PM, Steve Vinoski <vi...@ie...> wrote: > > > > On Mon, Sep 8, 2014 at 8:25 AM, Stefan Hellkvist <hel...@gm...> > wrote: > >> Hi everybody, >> >> I start yaws in embedded mode (inside a supervisor tree, as described on >> http://yaws.hyber.org/embed.yaws). For served files that does not have >> any file name extension (such as http://<host>/example) the default >> content type seems to be set to "text/plain". >> >> Is there some information anywhere on how I can configure the content >> type field for static files to be any content type that I like (for >> instance "text/html")? >> >> I see in the documentation (for instance >> http://yaws.hyber.org/internals.yaws) that one can set the >> #mime_types_info record of the sconf to override the default config in an >> appmod but I do not see any specifics on how to do this or how I would do >> this for the case where there is no file name extension. Any help, or >> pointers to examples, on how to do this would be much appreciated. >> > > If you pass a server config list to yaws_api:embedded_start_conf, you can > set the default mime type like this: > > yaws_api:embedded_start_conf(DocRoot, > [{mime_types_info, > [{default_type,"application/foo"}]}]) > > Replace "application/foo" with whatever you want the default mime type to > be for your server. Note that the second argument can also be a list of > lists for the case of multiple virtual servers, in which case you have to > set the mime_types_info element into each of the appropriate server list(s) > for your system. > > --steve > |