Bootstrap4 fileinput bug - Printable Version +- Atozed Forums (https://www.atozed.com/forums) +-- Forum: Atozed Software Products (https://www.atozed.com/forums/forum-1.html) +--- Forum: IntraWeb (https://www.atozed.com/forums/forum-3.html) +---- Forum: English (https://www.atozed.com/forums/forum-16.html) +----- Forum: IntraWeb General Discussion (https://www.atozed.com/forums/forum-4.html) +----- Thread: Bootstrap4 fileinput bug (/thread-1624.html) |
RE: Bootstrap4 fileinput bug - Rassamaha78 - 04-20-2020 (04-20-2020, 11:06 AM)TPiotr Wrote: I'm using IWStandAloneServer. SA(Indy HTTP ) work fine even in mode ParseFileUpload True , but i use HTTPSys type. RE: Bootstrap4 fileinput bug - TPiotr - 04-20-2020 In Full SA IWStandAloneServer1.Start(TSaServerIndy); option ParseFileUpload := True can't upload all files. In Http.sys option ParseFileUpload := True gives corrupted files. In Http.sys, all files have been saved, but: 1. Adds additional data: Code: ------WebKitFormBoundaryMviZ4UhsIZEcpH7F 2. Maybe something is wrong with Encoding. RE: Bootstrap4 fileinput bug - Rassamaha78 - 04-20-2020 1. When I switch my project to TIWStart.Execute (True); file transfer works fine, although WebKitFormBoyundary sections are added to the end of the file, removing them is not a problem, especially for picture files this is not critical. 2. When using TIWStartHSys.Execute (True); in the received file, one byte is lost at the beginning of the file (approximate address 0x00007F5A), this violates the integrity of the file and the picture is displayed with artifacts. I wrote about this in my first post. WebKitFormBoyundars sections are added at the end, as in the first case. I always set ParseFileUpload to True, if I change to False, then aRequest.Files. Count = 0. I would like to use HTTP.sys in my project, but so far I have to switch to Indy HTTP. RE: Bootstrap4 fileinput bug - Rassamaha78 - 04-29-2020 Is a solution expected in upcoming releases of IW ? RE: Bootstrap4 fileinput bug - Alexandre Machado - 05-01-2020 Can you provide a simple test case for this? I need a simple working project containing only IW files (no 3rd party other than IW Boostrap) which shows this problem. RE: Bootstrap4 fileinput bug - TPiotr - 05-01-2020 Hi, Compile and run IWUpload. Upload all files from "TestFilesToUpload" directory. See uploaded files in "uploaded" directory. RE: Bootstrap4 fileinput bug - Alexandre Machado - 05-01-2020 I don't know what's your version of fileinput.min.js. Can you please attach it to the project? RE: Bootstrap4 fileinput bug - TPiotr - 05-01-2020 I am using bootstrap-fileinput v4.3.2 I attach a zipped wwwroot folder and screenshot of problem. I tried too bootstrap-fileinput v5.0.9 and it doesn't work properly. RE: Bootstrap4 fileinput bug - Alexandre Machado - 05-02-2020 I can confirm that there is a problem which is highly visible when you upload PNG files (because 1 wrong byte is enough to make the file useless). I'm working on it and should have other information soon RE: Bootstrap4 fileinput bug - Alexandre Machado - 05-03-2020 Please install update 15.1.21: https://www.atozed.com/2020/05/intraweb-15-1-21/ |