Creating a portable version of Apache isn't difficult at all. I've done it for our own application. You can get away with using relative paths for everything (AFAIK) in httpd.conf
sub wrote: > Thanks for the suggestions re: standalone webserver and proxy server. You are > right though.. it's starting to get more tricky... more interesting too > though :) > > Cheers > > > Alexander Steitz wrote: >> Hi, >> >> On Tuesday 08 September 2009 sub wrote: >>> I want to create an App that check's a series of URL's to ensure the >>> health >>> of external websites >>> >>> It needs to check >>> >>> 1 status code (200, 500, 401, etc) >>> 2 text matching in the response body to prove that the content is what's >>> expected (make sure I didn't receive another page in error) >>> 3 check response headers would be great too but I'm pushing it I think. >>> >>> Now I can do all this with the qx.io.remote.Request Object and even use >>> an >>> qx.ui.embed.Iframe for visual confirmation. I also was considering >>> running >>> this out of the Test Runner (using qx.test.ui.LayoutTestCase) as it would >>> give a nice structured approach. >> You can only access URLs which are from the same origin. So if you want to >> check some external URLs you have to work with a proxy script which is >> installed at the web server which is also delivering your app. >> >>> Where I get stuck is that I actually wanted to run this off the file >>> system >>> rather than a web server so that a tester can deploy the tool where ever >>> needed (test different end points for connectivity etc) and run it >>> locally. >>> Remote Requests barf because due to the same Origin policy. The Iframe >>> still works but I don't think I can gather all the information I need >>> from >>> it. >> Remote Requests are also failing when the tester is using a local apache >> for >> example and tries to access e.g. "http://qooxdoo.org";. >> >> A possible solution can be to develop a kind of ready-to-run webserver >> setup >> which every tester can install. This package includes the web-server, the >> proxy script and your qooxdoo app. This way every tester has a local setup >> which he/she can use independenly. >> Drawback: Updates to such a setup are more complex. >> >> Just my 2cents. >> >> cheers, >> Alex >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
