|
|
Rank: Advanced Member
Groups: Member
Joined: 7/7/2014
Posts: 60
|
Hello,
We have a case where we are downloading large encrypted files with the EO browser. This has been working, and still works with one file exception. When decrypting this file we get a CRC error. Downloading the same file via the same web site with the Chrome browser instead of the .Net EO Browser works: file decrypts just fine. We've also directly downloaded the file straight out of SQL and it opens fine as well.
I'm checking to see if I am doing anything wonky inside our launcher that hosts the web site. While I don't think there is an issue with the EO web browser, that is the only place it seems to be having an issue. This is not working on the 3.0.100 version nor the 2015.2.37 version. I'll be updating the 2015 version to the latest in the next day or so, but I expect the same results.
So I am just throwing this out there in case there is something else I am overlooking.
thanks!
Craig Oliver
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
We can't think of anything that can cause that. The first thing you want to try is probably to use a network monitor to be sure that your server is indeed sending the correct contents. If you are sure that your server is sending the correct content, then you can PM us the Url and we can try to download the Url from here both using regular Google Chrome browser and our browser component. We should be able to debug into the source code of both of them to see what caused the difference.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/7/2014
Posts: 60
|
Thanks for the offer - you guys always step up. However, this is PHI /patient stuff, as well as secured via specific log ins, so sharing the URL is not possible.
I'm almost certain it has nothing to do per se with the EO browser as other files encrypted the same way work just fine. This just happens to be a larger file than most and the only place it is breaking is via the download using the EO browser engine.
No need to respond - if I figure out what the issue is I'll post it here.
thanks,
Craig
|
|