[Bug 4586] LWP retrieves empty page

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4586





------- Comment #16 from contact@athrasoft.com  2007-05-29 15:35 -------
(In reply to comment #15)

> We're not aware of any general problem with the Markup Validator and IIS 5.0.

Well, now you are.  \\:^)

--o-o-o-o-o-o-o--

> This appears to be a local configuration issue with your particular
> installation...

It seems W3C's Markup Validator is quite sensitive in this regard.
My server is reachable and is also content-readable all over the web (except
for
that tool).

--o-o-o-o-o-o-o--

> ...either due to how it is configured or due to an ISAPI filter or...

No filter at all. All default filters removed other than php interpreter (used
by my web-based community).

--o-o-o-o-o-o-o--

> The Markup Validator has no need to use HTTP Keep Alive because it only
> requests a single document from the remote server. HTTP Keep Alive is an
> optional method to optimize retreival of multiple documents from the same
> server within a short period of time. Both the CSS Validator and the Link
> Checker have need to fetch multiple documents to satisfy the request, so for
> these tools HTTP Keep Alive is an appropriate optimization technique to use.

Understood. that seems logical.
However, making it respect the keep-alive flag wouldn't hurt.

--o-o-o-o-o-o-o--

Terje, I'd like to thank you and to Olivier for all time spent on this.
I'll drop it, leave is as-is.

I have a feeling that, if my server was behind some *$oft company or similar,
this "feature" in the validator would deserve more attention - I mean inside
the code itself. Still don't see any inconvenience in respecting the
keep-alive.

After all, I have managed to make the guys see that there is a bad side-effect
of the validator's decision to not take that flag into account.
Also have learned a lot with you.

Thanks again and sorry for any inconvenience.

Best regards,
Paulo França

Received on Tuesday, 29 May 2007 15:35:44 UTC