As Pierre proposed, i'm trying to see what is going on with this error. Just to recap, the error only happened when i just chrome to acces to the app, with safari and firefox everything is ok.
I'm looking at the dump from whireshark, and i don't know what to look for. I see a "encrypted alert", but i read on the web that this message could be normal after a normal communication. I also noticed some tcp retransmission messsage. Do you have some tips for me?? Thanks Le 11 avril 2012 12:20, Benjamin Dreux <[email protected]> a écrit : > Hi > > What's happened here is that, you need to be logged to acces the resource. > The way the redirection is made, don't depend on me. It's a > functionality of our backend server. > > Once your your login is succesfully, the images could be requested correctly. > > For the error comming from qooxdoo, i'm sorry i respond to fast, but > the message shown earlier what already present when i start talking > about my issue. > > I will look once again to the proposition of Pierre > > Regards > > > > Le 11 avril 2012 11:38, thron7 <[email protected]> a écrit : >> Some observations: >> >> 1. I asked you one or two hours back if you get any relevant messages >> when running in source; you replied no, only a browser error, nothing >> from qooxdoo. Now I see you get multiple error messages from >> qx.ui.basic.Image ... >> >> 2. I tried to retrieved one of the image URLs in question, >> https://testdev.chaire-logiciel-libre.uqam.ca/resource/ifsr/icons/transaction.png. >> But what is returned from the server is *no image*. It is a complete >> HTML page, with form fields and buttons, supposedly a login form. THIS >> MUST NEVER HAPPEN. You cannot return an HTML page in place of an image. >> You can redirect. You can require some auth. But you should never return >> an entirely different resource in place of another. >> >> 3. Did you ever check that the resources themselves load on your side? >> >> 4. You should seriously consider what Pierre already suggested, to use a >> packet sniffer for the communication of your browser with the server, >> like Fiddler, CharlesProxy or Wireshark. >> >> Maybe you have to be logged in to get the real image. Maybe your server >> sometimes doesn't return images at all. I don't know ... >> >> I'm leaving this now to others. >> >> T. >> >> On 04/11/2012 05:09 PM, Benjamin Dreux wrote: >>> Thanks for the time you took to answer me >>> >>> For the rendering, the place is left blank. >>> The exact message is this >>> >>> 000385 qx.core.Init: Load runtime: 385ms >>> ifsr.js:30778002244 qx.core.Init: Main runtime: 1857ms >>> ifsr.js:30778002358 qx.core.Init: Finalize runtime: 114ms >>> https://testdev.chaire-logiciel-libre.uqam.ca/resource/ifsr/icons/transaction.pngFailed >>> to load resource >>> ifsr.js:30778032446 qx.ui.basic.Image[2725-0]: Image could not be >>> loaded: resource/ifsr/icons/transaction.png >>> ifsr.js:30778032447 qx.ui.basic.Image[2725-0]: Image could not be >>> loaded: resource/ifsr/icons/transaction.png >>> https://testdev.chaire-logiciel-libre.uqam.ca/resource/ifsr/icons/rm.pngFailed >>> to load resource >>> ifsr.js:30778032449 qx.ui.basic.Image[5000-0]: Image could not be >>> loaded: resource/ifsr/icons/rm.png >>> ifsr.js:30778032449 qx.ui.basic.Image[5000-0]: Image could not be >>> loaded: resource/ifsr/icons/rm.png >>> ifsr.js:30778032450 qx.ui.basic.Image[5020-0]: Image could not be >>> loaded: resource/ifsr/icons/rm.png >>> ifsr.js:30778032450 qx.ui.basic.Image[5020-0]: Image could not be >>> loaded: resource/ifsr/icons/rm.png >>> https://testdev.chaire-logiciel-libre.uqam.ca/resource/ifsr/icons/popup.pngFailed >>> to load resource >>> ifsr.js:30778032450 qx.ui.basic.Image[5121-0]: Image could not be >>> loaded: resource/ifsr/icons/popup.png >>> ifsr.js:30778032451 qx.ui.basic.Image[5121-0]: Image could not be >>> loaded: resource/ifsr/icons/popup.png >>> >>> as you can understand, ifsr is the name of the application >>> >>> Regards >>> >>> Le 11 avril 2012 10:58, thron7<[email protected]> a écrit : >>>> Ok, Daniel and I found out that the image url ist just set as a >>>> background url on the style of the containing element. After that, it's >>>> just the browser reacting on the style of a DOM element. So if that >>>> times out, it's outside of the qooxdoo run time. >>>> >>>> Is the image rendered, in spite of the error message? Or is the place >>>> left blank? >>>> >>>> Again, what is the exact error message you get? Is it "Failed to load >>>> resource"? Please quote verbatim. >>>> >>>> >>>> >>>> On 04/11/2012 04:16 PM, Benjamin Dreux wrote: >>>>> I didn't get additionnal message >>>>> >>>>> Le 11 avril 2012 09:51, thron7<[email protected]> a écrit : >>>>>> On 04/11/2012 02:57 PM, Benjamin Dreux wrote: >>>>>>> I don't get any more luck with the source version of the app. >>>>>>> I don't have a more detailed message >>>>>> Does that mean you didn't get the error in the source version? Or did >>>>>> you get it, but there was no additional console message, e.g. from the >>>>>> ImageLoader?! >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Better than sec? Nothing is better than sec when it comes to >>>>>> monitoring Big Data applications. Try Boundary one-second >>>>>> resolution app monitoring today. Free. >>>>>> http://p.sf.net/sfu/Boundary-dev2dev >>>>>> _______________________________________________ >>>>>> qooxdoo-devel mailing list >>>>>> [email protected] >>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>>>> >>>> ------------------------------------------------------------------------------ >>>> Better than sec? Nothing is better than sec when it comes to >>>> monitoring Big Data applications. Try Boundary one-second >>>> resolution app monitoring today. Free. >>>> http://p.sf.net/sfu/Boundary-dev2dev >>>> _______________________________________________ >>>> qooxdoo-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>> >>> >> >> ------------------------------------------------------------------------------ >> Better than sec? Nothing is better than sec when it comes to >> monitoring Big Data applications. Try Boundary one-second >> resolution app monitoring today. Free. >> http://p.sf.net/sfu/Boundary-dev2dev >> _______________________________________________ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > > -- > Benjamin Dreux > Analyste-Programmeur > Chaire de logiciel libre-Finance Social et solidaire > UQAM > Montréal -- Benjamin Dreux Analyste-Programmeur Chaire de logiciel libre-Finance Social et solidaire UQAM Montréal ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
