|
|
Posted by Alan J. Flavell on 05/15/06 19:53
On Mon, 15 May 2006, Andy Dingley <dingbat@codesmiths.com> wrote:
> That's not the same thing. Also Windows doesn't have alocal web
> server by default, you have to install one (typically PWS, or maybe
> Apache)
For those who develop on Windows, but host the results on an Apache
server (which *is* the most usual production web server, after all),
then I'd certainly recommend them installing Win32 Apache2 and using
it to mimic their part of the production web site as closely as
possible[1]
> For subtle bugs, looking at files in a filesystem is certainly NOT
> the same thing as a web server. You don't get HTTP headers, so you
> often see browsers behaving differently. It's OK for quick draft
> design work, but don't go bug-hunting this way.
Fully agree with that.
> omeldoid@gmail.com is getting ignored because he expects those who
> might otherwise help him, to do simple work that he's not prepared
> to do himself (placing it on a web server).
Definitely safest to host the test pages on a publicly accessible web
server *and* verify that the problem is still present, before
launching a question here, indeed. Nicest of course if the questioner
can boil the problem down into an uncluttered test case.
I lost count of the number of incidents of copy/paste errors in usenet
postings - which have either introduced some new problem that wasn't
the one they were looking for, or (as in that recent incident on the
uk web group) completely omitted the cause of the problem that they
*were* looking for. Complete waste of everybody's time - not only
their own.
cheers
[1] Yes, Virginia, it *is* possible to create a file called .htaccess
in Windows, even if some Windows applications try to convince you
otherwise! But it's necessary to take care over possible upper/lower
case incompatibilities between windows and production OSes.
--
Debugging package - may contain traces
Navigation:
[Reply to this message]
|