Project

General

Profile

Actions
Copy link

Bug #1834

closed

Invalid Content-Type sent when more than one mimetype.assign matches

Added by eryretqwewrqr almost 16 years ago. Updated over 8 years ago.

Status:
Fixed
Priority:
Normal
Category:
core
Target version:
1.4.40
ASK QUESTIONS IN Forums:

Description

On Debian my config contains:

include_shell "/usr/share/lighttpd/create-mime.assign.pl" 

mimetype.assign += (
    ".bz2" => "application/bzip2" 
…

Accidentally I've added same extension in mimetype.assign that was already generated from system's mime.types file.

This caused lighttpd to output both types in one header:

Content-Type: application/tar, application/bz2

This is not allowed in RFC 2616.

Related issues 1 (0 open — 1 closed)

Related to Bug #2685: add warning for duplicate array keys in configFixed2015-11-27Actions
Actions
Copy link
 #1

Updated by stbuehler almost 16 years ago

  • Status changed from New to Wontfix

Config design problem, won't fix - sry.

Actions
Copy link
 #2

Updated by gstrauss over 8 years ago

  • Related to Bug #2685: add warning for duplicate array keys in config added
Actions
Copy link
 #3

Updated by gstrauss over 8 years ago

  • Status changed from Wontfix to Fixed
  • Target version set to 1.4.40
commit 43da5818939817e00ca0128caee4a8b2d746a384
Author: Glenn Strauss <gstrauss@gluelogic.com>
Date:   Tue Mar 15 18:56:05 2016 +0000

    [core] configparser: error on duplicate keys in array merge (fixes #2685)

    From: Glenn Strauss <gstrauss@gluelogic.com>

    git-svn-id: svn://svn.lighttpd.net/lighttpd/branches/lighttpd-1.4.x@3103 152afb58-edef-0310-8abb-c4023f1b3aa9
Actions
Copy link

Also available in: Atom