404 Error — Please Help

[lytrotis]

We recently had a custom Joomla! 1.0 template created and installed by https://w3-markup.com. In the past, we've never had a problem with them but on this project they have been very slow and unresponsive. A major part of their service is to create w3 valid sites, however this site is displaying a "404 not found" error and they have not responded to any of our emails over the last several weeks about this. At this point, I've given up on them and am trying to figure out how to resolve this. At least, I just want to get w3 to at least read this site!?

This site is:

http://insidegrape.com/

W3 Error

Any thoughts on this would be much appreciated!

Thanks.

[olivier Thereaux]

Hello,

On 12-Aug-08, at 9:59 PM, lytrotis wrote:

> We recently had a custom Joomla! 1.0 template created and installed by
> https://w3-markup.com. In the past, we've never had a problem with  
> them but
> on this project they have been very slow and unresponsive. A major  
> part of
> their service is to create w3 valid sites, however this site is  
> displaying a
> "404 not found" error and they have not responded to any of our  
> emails over
> the last several weeks about this. At this point, I've given up on  
> them and
> am trying to figure out how to resolve this. At least, I just want  
> to get w3
> to at least read this site!?

The w3-markup company has nothing to do with the W3C or its validating  
tools - beyond, perhaps, the fact that they use our tools.
I suggest you keep trying to contact them directly and settle this  
issue.

regards,
olivier
--
olivier Thereaux - W3C - http://www.w3.org/People/olivier
W3C Open Source Software : http://www.w3.org/Status

[lytrotis]

Thanks. Yes, we realize that their company has nothing to do with W3C. Unfortunately, they have been unreliable and unresponsive on this project. Continuing to try and hound them to resolve this is unfortunately, no longer a viable option. I intend to find another third-party developer for this issue and other future development, however I'm trying to learn more about this issue before I contact another developer.

olivier Thereaux wrote:

Hello,

On 12-Aug-08, at 9:59 PM, lytrotis wrote:

> We recently had a custom Joomla! 1.0 template created and installed by
> https://w3-markup.com. In the past, we've never had a problem with  
> them but
> on this project they have been very slow and unresponsive. A major  
> part of
> their service is to create w3 valid sites, however this site is  
> displaying a
> "404 not found" error and they have not responded to any of our  
> emails over
> the last several weeks about this. At this point, I've given up on  
> them and
> am trying to figure out how to resolve this. At least, I just want  
> to get w3
> to at least read this site!?

The w3-markup company has nothing to do with the W3C or its validating  
tools - beyond, perhaps, the fact that they use our tools.
I suggest you keep trying to contact them directly and settle this  
issue.

regards,
olivier
--
olivier Thereaux - W3C - http://www.w3.org/People/olivier
W3C Open Source Software : http://www.w3.org/Status

[Sierk Bornemann-2]

Am 13.08.2008 um 13:58 schrieb lytrotis:

> Yes, we realize that their company has nothing to do with W3C.

Since you are obviously knowing, that w3.org (at least the staff,  
members and readers of the w3 validator) isn't the right recipient for  
your desire, so why do you address them anyway?
Please address and blame https://w3-markup.com/ (and/or developers  
around that web space) and no one else.

--
Sierk Bornemann
WWW:              http://sierkbornemann.de/

[Chuck Houpt]

(Although this thread is a bit off-topic, I thought I'd respond  
because it is common to get confused about the different ways web  
browsers and web tools handle HTTP result codes)

Hi lytrotis,

The problem you are seeing is because the front page of  
insidegrape.com is always returning the 404 (Page Not Found) error  
code. The HTTP header is listed below (fetched with the curl tool).  
Because of the 404 code, the Validator stops checking the page.

Regular web browsers do not check or indicate anything when an error  
code is received - they just display the received page as normal. Of  
course, typically the page received with a 404 code is a page  
explaining that the requested URL couldn't be found (and maybe  
offering a site map or search). In the case of insidegrape.com, the  
normal front page is being sent with a 404 code.

Tools like the W3C Validator do check the HTTP result code, so it does  
not validate a page when  it receives a 404 code. Note that sub-pages  
of insidegrape.com return normal result codes, so they can be  
validated. For example:

http://validator.w3.org/check?uri=http://insidegrape.com/index.php?
option=com_content&task=blogcategory&id=37&Itemid=96

Possibly the 404 code on the front page is a bug or it is set to  
prevent robots and other automated tools from visiting the site during  
development.

Cheers - Chuck
http://chuck.habilis.net

Header Dump:

% curl -I http://insidegrape.com/

HTTP/1.1 404 Not Found
Date: Wed, 13 Aug 2008 12:27:09 GMT
Server: Apache/2.0.63
X-Powered-By: PHP/5.2.6
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-
check=0
Pragma: no-cache
Set-Cookie: 93a4cd5d4ba7ac4f27dac967d3e05e88=-; path=/
Last-Modified: Wed, 13 Aug 2008 12:27:09 GMT
Content-Type: text/html

[lytrotis]

Chuck, thanks for the thorough response. That actually makes a lot of sense. Not that I can personally do anything about it =) at least I have a clearer idea of what's going and how to get it resolved.

Thanks again.

Chuck Houpt wrote:

(Although this thread is a bit off-topic, I thought I'd respond  
because it is common to get confused about the different ways web  
browsers and web tools handle HTTP result codes)

Hi lytrotis,

The problem you are seeing is because the front page of  
insidegrape.com is always returning the 404 (Page Not Found) error  
code. The HTTP header is listed below (fetched with the curl tool).  
Because of the 404 code, the Validator stops checking the page.

Regular web browsers do not check or indicate anything when an error  
code is received - they just display the received page as normal. Of  
course, typically the page received with a 404 code is a page  
explaining that the requested URL couldn't be found (and maybe  
offering a site map or search). In the case of insidegrape.com, the  
normal front page is being sent with a 404 code.

Tools like the W3C Validator do check the HTTP result code, so it does  
not validate a page when  it receives a 404 code. Note that sub-pages  
of insidegrape.com return normal result codes, so they can be  
validated. For example:

http://validator.w3.org/check?uri=http://insidegrape.com/index.php?
option=com_content&task=blogcategory&id=37&Itemid=96

Possibly the 404 code on the front page is a bug or it is set to  
prevent robots and other automated tools from visiting the site during  
development.

Cheers - Chuck
http://chuck.habilis.net

Header Dump:

% curl -I http://insidegrape.com/

HTTP/1.1 404 Not Found
Date: Wed, 13 Aug 2008 12:27:09 GMT
Server: Apache/2.0.63
X-Powered-By: PHP/5.2.6
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-
check=0
Pragma: no-cache
Set-Cookie: 93a4cd5d4ba7ac4f27dac967d3e05e88=-; path=/
Last-Modified: Wed, 13 Aug 2008 12:27:09 GMT
Content-Type: text/html

[olivier Thereaux]

Hello,

On 13-Aug-08, at 9:16 AM, Chuck Houpt wrote:
> The problem you are seeing is because the front page of  
> insidegrape.com is always returning the 404 (Page Not Found) error  
> code. The HTTP header is listed below (fetched with the curl tool).  
> Because of the 404 code, the Validator stops checking the page.


Indeed. Note also that the validator has an option to "check error  
pages", if that can be useful.

--
olivier