- Feb 01, 2014
-
-
Sergey Lyubka authored
-
- Jan 30, 2014
-
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
- Jan 29, 2014
-
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
- Jan 28, 2014
-
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
- Jan 27, 2014
-
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
- Jan 26, 2014
-
-
Sergey Lyubka authored
-
- Jan 25, 2014
-
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
- Jan 24, 2014
-
-
Sergey Lyubka authored
-
Sergey Lyubka authored
allow to define a default mime-type
-
Andrea Guzzo authored
instead of using a configuration option
-
Andrea Guzzo authored
instead of always returning 'text/plain' To allow setting a different default mime-type the mg_get_mime_type() api has been extended to require an mg_server parameter. Note that using a static global as default mime type wouldn't have allowed us to control it via a configuration option because there is not global initialization phase and configuration options are provided (and specific) to each server instance. This means that different servers can be configured to use a different default mime-type (which is also a desired behaviour in many scenarios) when lookup fails.
- Jan 23, 2014
-
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
- Jan 22, 2014
-
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
- Jan 20, 2014
-
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-
Sergey Lyubka authored
-