Path: csiph.com!usenet.pasdenom.info!news.albasani.net!news2.arglkargh.de!noris.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="ISO-8859-1" Message-ID: <7238984.617k9mAqVa@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Sat, 06 Oct 2012 08:48:23 +0200 User-Agent: KNode/4.4.11 Content-Transfer-Encoding: 7Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. <2610175.x4FWaXcEle@PointedEars.de> Followup-To: comp.lang.javascript MIME-Version: 1.0 Lines: 25 NNTP-Posting-Date: 06 Oct 2012 08:48:24 CEST NNTP-Posting-Host: 89e42f0b.newsspool4.arcor-online.net X-Trace: DXC=QbRYXZ1O2O7^cW`WBF>WQ<4IUKK0YMeRZD8g?;6jV]`ah8QGo> X-Complaints-To: usenet-abuse@arcor.de Xref: csiph.com comp.lang.javascript:16424 Patricia Shanahan wrote: > RFC 6068, "The 'mailto' URI Scheme" says "Only a limited set of header > fields such as Subject and Keywords, as well as Body, are believed to be > both safe and useful in the general case." > > I've tested with Firefox as browser and Thunderbird as mail client. The > content type header in the message as delivered is "text/plain; > charset=ISO-8859-1; format=flowed" regardless of my attempts to specify > a multi-part content type in the URI. I had not considered the requirement for the main `Content-Type' header field of multi-part messages. The question remains why it would be acceptable to send the data over the Internet via e-mail to an SMTP server, but not over the Internet to an HTTP server. PointedEars -- var bugRiddenCrashPronePieceOfJunk = ( navigator.userAgent.indexOf('MSIE 5') != -1 && navigator.userAgent.indexOf('Mac') != -1 ) // Plone, register_function.js:16