thanks to g*sales and a comment on our mite.api blog we do know the reason for the mysterious numbers that appeared since our upgrade to rails3. They come from the new encoding: "chunked"
The numbers are the content lengths of the separated packages, this also explains the "0" at the end, which shows the end of the transfer.
Meanwhile g*sales published a hotfix that goes around the issue by requesting HTTP/1.0 instead of 1.1, you can find it here. Maybe it makes sense to incorporate the fix into mite.php?
Hey Thomas,
thanks to g*sales and a comment on our mite.api blog we do know the reason for the mysterious numbers that appeared since our upgrade to rails3. They come from the new encoding: "chunked"
The numbers are the content lengths of the separated packages, this also explains the "0" at the end, which shows the end of the transfer.
Meanwhile g*sales published a hotfix that goes around the issue by requesting HTTP/1.0 instead of 1.1, you can find it here. Maybe it makes sense to incorporate the fix into mite.php?
http://forum.gsales.de/showthread.php?1992-Hotfix-f%FCr-Probleme-mit-dem-mite-Import&p=12156#post12156
I also found this post that explains the issue and suggests some ways to go around it: http://bytes.com/topic/php/answers/504363-disallow-http-chunked-transfer#post1959833