--K8nIJk4ghYZn606h
Content-Type: multipart/mixed; boundary="17pEHd4RhPHOinZp"
Content-Disposition: inline


--17pEHd4RhPHOinZp
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

the attached patch adds support for the 'Content-type' header on
HTTP PUT operations.

I can't find any spec/rfc where exactly is stated that HTTP PUT must
provide a content-type, however some server expect it from their
clients, so we should allow the client applications to use
  job->addMetaData()
to make these servers happy.

Objections?

Ciao,
Tobias
--=20
Separate politics from religion and economy!
The Council of the European Union is an undemocratic and illegal institutio=
n!

--17pEHd4RhPHOinZp
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: attachment; filename="kio_http.patch"
Content-Transfer-Encoding: quoted-printable

Index: http.cc
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- http.cc	(Revision 629391)
+++ http.cc	(Arbeitskopie)
@@ -2491,7 +2491,7 @@
       header +=3D "\r\n";
     }
=20
-    if (m_request.method =3D=3D HTTP_POST)
+    if (m_request.method =3D=3D HTTP_POST || m_request.method =3D=3D HTTP_=
PUT)
     {
       header +=3D metaData("content-type");
       header +=3D "\r\n";

--17pEHd4RhPHOinZp--

--K8nIJk4ghYZn606h
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFF5arUSvFUKpY6VLARAotKAJ9qtocsskhZyJLdTrxKRw4EcOrw5ACglSql
82XGrOFGZDdnEQjX2g9cU6g=
=yqvU
-----END PGP SIGNATURE-----

--K8nIJk4ghYZn606h--

		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de