a8bc834077
Mime/PartHeaders now handle both Content-ID and Content-id according to W3 specs
2017-06-12 15:14:28 +02:00
f74e4b08ce
Mime Parser: throws Exception with MimePartMessage contents
2017-06-12 00:28:27 +02:00
2264e329a1
Added phing for running tests & fixed issues in order to pass the tests
2017-06-07 15:50:04 +02:00
ab83642f06
Parser fix: single line MimeMessages are now parsed correctly
2017-04-06 15:51:29 +02:00
564005da93
SoapServer/Client now handle binary files correctly & large tests/fixtures update
...
Soap Server and Client were breaking binary files during transfer due to invalid Mime Message Parser. Now is it working fine with no errors, but the message parser is about to be rewritten into a better form.
2017-04-04 18:36:18 +02:00
4edc46e67f
Parser fix - MimeMessages with CRLF caused iconv_mime_decode throwing Exceptions
2017-02-17 15:06:06 +01:00
aee034791e
SoapClient large refactoring & tests update
2017-02-14 16:01:39 +01:00
476813e9bb
MIME parts now contain only LF (was CRLF)
2016-11-29 18:55:55 +01:00
f57239ad0d
MultiPart Boundary generator changed
2016-11-24 15:18:00 +01:00
10caf27da3
MultiPart ContentId is now in different format
2016-11-24 15:00:46 +01:00
1224f5f40f
Content-Location added for attachment parts
2016-11-24 12:45:17 +01:00
c4d993585f
SoapServer now handles get WSDL requests
2016-11-09 13:43:18 +01:00
84c37b1d24
Soap server with attachments refactoring
2016-11-08 15:42:52 +01:00
b78bf408bf
Reorganized directories structure
2013-07-19 17:01:55 +02:00
