Re: mime.types.conf int lighttpd
On Mon, 27 Feb 2012, Elan Ruusamäe wrote: [...] Are you going to fix it? It's quite long time -- pozdr. Paweł Gołaszewski jid:bluesatjabberdotgdadotpl -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free.___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On 20.03.2012 12:23, Pawe? Go?aszewski wrote: On Mon, 27 Feb 2012, Elan Ruusamäe wrote: [...] Are you going to fix it? It's quite long time i was waiting your reply to my question... http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-February/022491.html followed further discussion/explanation, but no real reply to question! -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On Tue, 20 Mar 2012, Elan Ruusamäe wrote: [...] Are you going to fix it? It's quite long time i was waiting your reply to my question... http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-February/022491.html followed further discussion/explanation, but no real reply to question! I don't want to argue - I just want to have it *working* again. You broke, you fix. I don't know the internals and I don't want to know. Fix it or revert your previous change. -- pozdr. Paweł Gołaszewski jid:bluesatjabberdotgdadotpl -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free.___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On 20.03.2012 15:58, Paweł Gołaszewski wrote: On Tue, 20 Mar 2012, Elan Ruusamäe wrote: [...] Are you going to fix it? It's quite long time i was waiting your reply to my question... http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-February/022491.html followed further discussion/explanation, but no real reply to question! I don't want to argue - I just want to have it *working* again. You broke, you fix. I don't know the internals and I don't want to know. Fix it or revert your previous change. i proposed a solution, is that fix acceptable? -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On Tue, 20 Mar 2012, Elan Ruusamäe wrote: [...] Are you going to fix it? It's quite long time i was waiting your reply to my question... http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-February/022491.html followed further discussion/explanation, but no real reply to question! I don't want to argue - I just want to have it *working* again. You broke, you fix. I don't know the internals and I don't want to know. Fix it or revert your previous change. i proposed a solution, is that fix acceptable? Will it destroy _working_ configurations? If yes (IMvHO it's the case) then - it's not acceptable. If this that option is apaches add default charset equivalent - you have anwer from me and baggins. What is the _rationale_ for that change? What more do you want to know?? -- pozdr. Paweł Gołaszewski jid:bluesatjabberdotgdadotpl -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free.___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On 20.03.2012 18:34, Paweł Gołaszewski wrote: On Tue, 20 Mar 2012, Elan Ruusamäe wrote: [...] Are you going to fix it? It's quite long time i was waiting your reply to my question... http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-February/022491.html followed further discussion/explanation, but no real reply to question! I don't want to argue - I just want to have it *working* again. You broke, you fix. I don't know the internals and I don't want to know. Fix it or revert your previous change. i proposed a solution, is that fix acceptable? Will it destroy _working_ configurations? If yes (IMvHO it's the case) then - it's not acceptable. new %config(noreplace) is deployed as .rpmnew, so no, if you made changes to that file If this that option is apaches add default charset equivalent - you have anwer from me and baggins. it's equivalent yes, so same issues are present there What is the _rationale_ for that change? utf-8 as default encoding, to all documents. there's no way specify encoding as html tag for .txt files What more do you want to know?? i wanted to know is that change acceptable, or you still find that me breaking your window and violating your cat. -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On Tue, 20 Mar 2012, Elan Ruusamäe wrote: [...] Are you going to fix it? It's quite long time i was waiting your reply to my question... http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-February/022491.html followed further discussion/explanation, but no real reply to question! I don't want to argue - I just want to have it *working* again. You broke, you fix. I don't know the internals and I don't want to know. Fix it or revert your previous change. i proposed a solution, is that fix acceptable? Will it destroy _working_ configurations? If yes (IMvHO it's the case) then - it's not acceptable. new %config(noreplace) is deployed as .rpmnew, so no, if you made changes to that file working doesn't mean changed Most people don't need to touch that config. Make it commented out, don't break working sites. If this that option is apaches add default charset equivalent - you have anwer from me and baggins. it's equivalent yes, so same issues are present there It's not acceptable then. Like in apache. You had that answer earlier. What is the _rationale_ for that change? utf-8 as default encoding, to all documents. there's no way specify encoding as html tag for .txt files Why should it be? In most cases users don't need to display plain txt files. They need working meta tags in html. What more do you want to know?? i wanted to know is that change acceptable, or you still find that me breaking your window and violating your cat. I don't care cats - leave my dog :P -- pozdr. Paweł Gołaszewski jid:bluesatjabberdotgdadotpl -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free.___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On 20/03/12 20:45, Paweł Gołaszewski wrote: What is the_rationale_ for that change? utf-8 as default encoding, to all documents. there's no way specify encoding as html tag for .txt files Why should it be? In most cases users don't need to display plain txt files. They need working meta tags in html. most case users is rather relative to be an option :) it's as strong statement as most of the world prefers utf-8 :D -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On 25/02/12 23:35, Paweł Gołaszewski wrote: On Sat, 25 Feb 2012, g...@pld-linux.org wrote: There is problem with recent change in lighttpd-mime.types.sh (it generates mime.types.conf). [...] revision 1.3 date: 2012/01/22 20:52:51; author: glen; state: Exp; lines: +15 -1; kopt: kv; commitid: 64d94f1c7723ee01; filename: lighttpd-mime.types.sh; - add charset to text content-types; default as utf8 [...] There is added header: # charset used for text/* mimetypes mimetype_textcharset = utf-8 ...and some charset= + mimetype_textcharset entries. It causes problems because encoding is not detected in pages, always utf-8 is used, no matter what header in html is set. Tested on AC. This should be reversed... perhaps then mimetype_charsetheader = ; charset=\utf-8\ to be able to leave it empty meaning no charset is enforced Any docs about that option? I can't find anything about that... Any encoding set in user files CAN'T be overwriten... P.S.: I wanted revert your changes today... docs of what? mimetype.assign = ()? there are no docs, in pld mimetype.assign is generated from /etc/mime.types, and the charset header is just programmed using string concat that lighttpd config engine supports. so, that go with that last option (mimetype_charsetheader = ; charset=\utf-8\) ?, better than completely reverting... and you seem to mean by user files html meta http equiv? http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs:Configuration http://redmine.lighttpd.net/projects/lighttpd/wiki/Mimetype.assignDetails -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On 25/02/12 23:35, Paweł Gołaszewski wrote: Any docs about that option? I can't find anything about that... equivalent in apache what was wanted to achieve in lighttpd: http://httpd.apache.org/docs/2.4/mod/core.html#adddefaultcharset -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On Mon, 27 Feb 2012, Elan Ruusamäe wrote: Any docs about that option? I can't find anything about that... equivalent in apache what was wanted to achieve in lighttpd: http://httpd.apache.org/docs/2.4/mod/core.html#adddefaultcharset I know that option and in apache it causes problems too. -- pozdr. Paweł Gołaszewski jid:bluesatjabberdotgdadotpl -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free.___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On Mon, 27 Feb 2012, Elan Ruusamäe wrote: There is problem with recent change in lighttpd-mime.types.sh (it generates mime.types.conf). [...] revision 1.3 date: 2012/01/22 20:52:51; author: glen; state: Exp; lines: +15 -1; kopt: kv; commitid: 64d94f1c7723ee01; filename: lighttpd-mime.types.sh; - add charset to text content-types; default as utf8 [...] There is added header: # charset used for text/* mimetypes mimetype_textcharset = utf-8 ...and some charset= + mimetype_textcharset entries. It causes problems because encoding is not detected in pages, always utf-8 is used, no matter what header in html is set. Tested on AC. This should be reversed... perhaps then mimetype_charsetheader = ; charset=\utf-8\ to be able to leave it empty meaning no charset is enforced Any docs about that option? I can't find anything about that... docs of what? mimetype.assign = ()? no, mimetype_charsetheader so, that go with that last option (mimetype_charsetheader = ; charset=\utf-8\) ?, better than completely reverting... and you seem to mean by user files html meta http equiv? yep, meta. -- pozdr. Paweł Gołaszewski jid:bluesatjabberdotgdadotpl -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free.___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On Mon, 27 Feb 2012, Elan Ruusamäe wrote: On 25/02/12 23:35, Paweł Gołaszewski wrote: Any docs about that option? I can't find anything about that... equivalent in apache what was wanted to achieve in lighttpd: http://httpd.apache.org/docs/2.4/mod/core.html#adddefaultcharset Adding this in apache breaks existing configs. Big time. -- Jan Rękorajski | PLD/Linux SysAdm | http://www.pld-linux.org/ bagginsatmimuw.edu.pl bagginsatpld-linux.org ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On Thu, Feb 16, 2012 at 08:45:39AM +0100, Paweł Gołaszewski wrote: There is added header: # charset used for text/* mimetypes mimetype_textcharset = utf-8 ...and some charset= + mimetype_textcharset entries. It causes problems because encoding is not detected in pages, always utf-8 is used, no matter what header in html is set. And that is exactly how that is supposed to work (but probably not what the change author wanted). Charset defined in the Content-Type HTTP header takes precedence over anything else, especially the meta/ tag in the HTML. In the ideal world meta/ would never be used for this purpose and 'charset' in Content-Type should be set, but in the real world many rely on the meta/ tag and forcing charset into the Content-Type header only breaks things. Greets, Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On Mon, Feb 27, 2012 at 12:42:47PM +0100, Paweł Gołaszewski wrote: On Mon, 27 Feb 2012, Elan Ruusamäe wrote: Any docs about that option? I can't find anything about that... equivalent in apache what was wanted to achieve in lighttpd: http://httpd.apache.org/docs/2.4/mod/core.html#adddefaultcharset I know that option and in apache it causes problems too. Because most people do not understand this option, the Content-Type header and the 'meta http-equiv/' tag. Greets, Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On 27.02.2012 15:02, Jacek Konieczny wrote: On Thu, Feb 16, 2012 at 08:45:39AM +0100, Paweł Gołaszewski wrote: There is added header: # charset used for text/* mimetypes mimetype_textcharset = utf-8 ...and some charset= + mimetype_textcharset entries. It causes problems because encoding is not detected in pages, always utf-8 is used, no matter what header in html is set. And that is exactly how that is supposed to work (but probably not what the change author wanted). Charset defined in the Content-Type HTTP header takes precedence over anything else, especially the meta/ tag in the HTML. In the ideal world meta/ would never be used for this purpose and 'charset' in Content-Type should be set, but in the real world many rely on the meta/ tag and forcing charset into the Content-Type header only breaks things. yes exactly, and to satisfy both worlds, i propose to add new env var, that can be left empty by default and interested ones can set value which is appeneded text/* mime types. mimetype_charsetheader = ; charset=\utf-8\ instead of current: mimetype_textcharset = utf-8 and mime.types would contain: .wmls= text/vnd.wap.wmlscript + mimetype_textcharset, instead of .wmls= text/vnd.wap.wmlscript; charset= + mimetype_textcharset, -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On 16/02/12 09:45, Paweł Gołaszewski wrote: There is problem with recent change in lighttpd-mime.types.sh (it generates mime.types.conf). [...] revision 1.3 date: 2012/01/22 20:52:51; author: glen; state: Exp; lines: +15 -1; kopt: kv; commitid: 64d94f1c7723ee01; filename: lighttpd-mime.types.sh; - add charset to text content-types; default as utf8 [...] There is added header: # charset used for text/* mimetypes mimetype_textcharset = utf-8 ...and some charset= + mimetype_textcharset entries. It causes problems because encoding is not detected in pages, always utf-8 is used, no matter what header in html is set. Tested on AC. This should be reversed... perhaps then mimetype_charsetheader = ; charset=\utf-8\ to be able to leave it empty meaning no charset is enforced -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mime.types.conf int lighttpd
On Sat, 25 Feb 2012, g...@pld-linux.org wrote: There is problem with recent change in lighttpd-mime.types.sh (it generates mime.types.conf). [...] revision 1.3 date: 2012/01/22 20:52:51; author: glen; state: Exp; lines: +15 -1; kopt: kv; commitid: 64d94f1c7723ee01; filename: lighttpd-mime.types.sh; - add charset to text content-types; default as utf8 [...] There is added header: # charset used for text/* mimetypes mimetype_textcharset = utf-8 ...and some charset= + mimetype_textcharset entries. It causes problems because encoding is not detected in pages, always utf-8 is used, no matter what header in html is set. Tested on AC. This should be reversed... perhaps then mimetype_charsetheader = ; charset=\utf-8\ to be able to leave it empty meaning no charset is enforced Any docs about that option? I can't find anything about that... Any encoding set in user files CAN'T be overwriten... P.S.: I wanted revert your changes today... -- pozdr. Paweł Gołaszewski jid:bluesatjabberdotgdadotpl -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free.___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
mime.types.conf int lighttpd
There is problem with recent change in lighttpd-mime.types.sh (it generates mime.types.conf). [...] revision 1.3 date: 2012/01/22 20:52:51; author: glen; state: Exp; lines: +15 -1; kopt: kv; commitid: 64d94f1c7723ee01; filename: lighttpd-mime.types.sh; - add charset to text content-types; default as utf8 [...] There is added header: # charset used for text/* mimetypes mimetype_textcharset = utf-8 ...and some charset= + mimetype_textcharset entries. It causes problems because encoding is not detected in pages, always utf-8 is used, no matter what header in html is set. Tested on AC. This should be reversed... -- pozdr. Paweł Gołaszewski jid:bluesatjabberdotgdadotpl -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free.___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
