Now I have had time to check how Wireshark can be used to extract transferred files.
So I could get the file out from the FireFox transfer's logfile:
The file is completely contained within the Wireshark log but it is preceded by the following text (note line breaks shown in < >:
Then I opened the Wireshark log for transferring with the Config program using Indy.
Again I saved the contained file object.
This is what I found:
It looks like the only difference is that Indy adds
just before the file data whereas FireFox does not.
So I could get the file out from the FireFox transfer's logfile:
The file is completely contained within the Wireshark log but it is preceded by the following text (note line breaks shown in < >:
Code:
"-----------------------------94861119430606
Content-Disposition: form-data; name="update"; filename="DHT_MONITOR.bin"
Content-Type: application/octet-stream<0D 0A 0D 0A>"
Binary data identical to original file
After the file ends there is another chunk looking like this:
"<0D 0A>-----------------------------94861119430606--<0D 0A>"
Then I opened the Wireshark log for transferring with the Config program using Indy.
Again I saved the contained file object.
This is what I found:
Code:
Preamble before binary data:
"----------050218090850543
Content-Disposition: form-data; name="update"; filename="DHT_MONITOR.bin"
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary<0D 0A 0D 0A>"
Binary data identical to original file
Postamble after the file data:
"<0D 0A>----------050218090850543--<0D 0A>"
It looks like the only difference is that Indy adds
Code:
Content-Transfer-Encoding: binary
just before the file data whereas FireFox does not.