Hi,
I have been trying to figure out what is causing the above mentioned
problems under IIS and I have made some progress:
about the PDF generation, it was an application bug. I was using a
relative path to refer to the styles file (.CSS) for the report. Now,
using an absolute path to refer to the styles file, the PDF file is
being generated correctly. Sorry about that.
about the WFileUpload widget problem, I have tested with different files
and the problem seems to arise every time that I try to load a file
bigger than 50Kb. I have compiled widgetgallery to run under IIS and I
get the same results. Every time that I try to upload a file bigger than
50Kb, the application crashes causing the application freeze or restart
(randomly) and at IIS level the application pool gets stopped
about the WFileResource widget problem, what I am trying to do is simply
display in a separate browser tab an existing file (.pdf, .jpg or
others) that is selected by the application user. The problem seems to
be that no matter the file name that is informed to the WFileResource
(relative, absolute, as an URL), the ISAPI connector adds the full site
path as file name prefix (for instance, if you try to surf from the same
machine where the application is running, the application tries to open
the file at localhost/application/application.dll/<file name>
As I commented before, using the built-in httpd connector both
WFileUpload and WFileResource work ok.
I would appreciate any comments or clues regarding WFileUpload and
WFileResource problems under IIS.
Thanks. Best regards.
________________________
Mario Diethelm Guallar
------ Original Message ------
From: "Mario Diethelm Guallar" <mariodiethe...@gmail.com>
To: witty-interest@lists.sourceforge.net
Sent: 01-04-2015 19:31:23
Subject: WFileUpload and WFileResource objects problems under IIS
Besides the problem related to PFD generation using the ISAPI connector
commented in a previous e-mail (always gets a zero bytes corrupted PDF
file), I am experiencing problems with WFileUpload and WFileResource
objects under IIS.
Every time that I start a file uploading to the server using the
WFileUpLoad widget, the application crashes while the WProgressBar
widget is showing the upload progress (at random levels). The
application then starts a completely new session.
In a similar way, the WFileResource object always ends with an HTTP
404.0 error every time that I try to display a file (PDF, .jpg or any
other). The application is using absolute paths to specify each file.
The same application widgets work just fine using the built-in httpd
connector.
Any idea about what is going on?
thanks. Best regards.
________________________
Mario Diethelm Guallar
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
