CLOSED RE: [WSG] W3C REFERER FIX?

2004-11-30 Thread Sam Hutchinson
yeah thanks but I think its the firewall, I know that happens if you try a
local page. this is a live page we are talking about. looks like the php
snippets suggested earlier are the way forward.

thanks for averybody's support on this string. i'm now closing it.

ta


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Richard Czeiger
Sent: Monday, November 29, 2004 11:20
To: [EMAIL PROTECTED]
Subject: Re: [WSG] W3C REFERER FIX?


Hi All - I've actually come across this before as well.
But for my machine, this error only happens when trying to validate pages
sitting on my hard-drive.
The link is for the form that checks online pages. Upload your page to a
server and try again  :o)

You can get heaps of bookmarklets that will help you validate your page
while in development.
These access the W3C's Validate by Upload form.

Hope this helps  :o)

Richard

**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**




**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



[WSG] W3C REFERER FIX?

2004-11-29 Thread Sam Hutchinson
W3C validation - pages validate when I run the URL through the validator,
but for some reason my pages and Logo's linking to
http://validator.w3.org/check?uri=referer has stopped working in IE (6.02) -
anyone else seen this, or know of a decent workaround?!?!

It still works in Mozilla and the like. Oh I hate Microsoft.

Error message follows:



No Referer header found!

You have requested we check the referring page, but your browser did not
send the HTTP Referer header field. This can be for several reasons, but
most commonly it is because your browser does not know about this header,
has been configured not to send one, or is behind a proxy or firewall that
strips it out of the request before it reaches us.

This is not an error in the referring page!

**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



RE: [WSG] W3C REFERER FIX?

2004-11-29 Thread Patrick Lauke
 From: Sam Hutchinson

 W3C validation - pages validate when I run the URL through 
 the validator,
 but for some reason my pages and Logo's linking to
 http://validator.w3.org/check?uri=referer has stopped working 
 in IE (6.02) -
 anyone else seen this, or know of a decent workaround?!?!

I'll have a stab in the dark and say that it's probably a
Windows XP Service Pack 2 issue - either a new security setting in IE,
or something that the built-in firewall is now blocking. I've also
had a similar scenario after installing Norton Internet Security (which
strips referer headers before they're sent out), but that would normally
affect all browsers, not just IE.

If at all possible, a fix would be to use a server-side language to
explicitly write out the current document's URL in the link.

Patrick

Patrick H. Lauke
Webmaster / University of Salford
http://www.salford.ac.uk
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



Re: [WSG] W3C REFERER FIX?

2004-11-29 Thread Johannes Reiss
I have IE 6.02 too, but still SP 1 and all is ok!

greetings,
johannes


- Original Message - 
From: Patrick Lauke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, November 29, 2004 2:42 PM
Subject: RE: [WSG] W3C REFERER FIX?


 From: Sam Hutchinson

 W3C validation - pages validate when I run the URL through 
 the validator,
 but for some reason my pages and Logo's linking to
 http://validator.w3.org/check?uri=referer has stopped working 
 in IE (6.02) -
 anyone else seen this, or know of a decent workaround?!?!

I'll have a stab in the dark and say that it's probably a
Windows XP Service Pack 2 issue - either a new security setting in IE,
or something that the built-in firewall is now blocking. I've also
had a similar scenario after installing Norton Internet Security (which
strips referer headers before they're sent out), but that would normally
affect all browsers, not just IE.

If at all possible, a fix would be to use a server-side language to
explicitly write out the current document's URL in the link.

Patrick

Patrick H. Lauke
Webmaster / University of Salford
http://www.salford.ac.uk
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



RE: [WSG] W3C REFERER FIX?

2004-11-29 Thread Sam Hutchinson
yeah it works on my slave machine running sp1, but I tend not to have that
connected, as it will just get eaten by the web (yours is still alive?). it
looks like it is a sp2 IE thing stripping the headers out. amongst other
things. this in itself is an example of a browser/OS affecting
accessibility.

I honestly liked IE for a while there, and I know most of my clients use it
so its important that we all have to still pander to the dreaded MS.

Cheers All. Will post a workaround when i've made it.

Sam
---
www.sammyco.co.uk




-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Johannes Reiss
Sent: Monday, November 29, 2004 02:01
To: [EMAIL PROTECTED]
Subject: Re: [WSG] W3C REFERER FIX?


I have IE 6.02 too, but still SP 1 and all is ok!

greetings,
johannes


- Original Message -
From: Patrick Lauke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, November 29, 2004 2:42 PM
Subject: RE: [WSG] W3C REFERER FIX?


 From: Sam Hutchinson

 W3C validation - pages validate when I run the URL through
 the validator,
 but for some reason my pages and Logo's linking to
 http://validator.w3.org/check?uri=referer has stopped working
 in IE (6.02) -
 anyone else seen this, or know of a decent workaround?!?!

I'll have a stab in the dark and say that it's probably a
Windows XP Service Pack 2 issue - either a new security setting in IE,
or something that the built-in firewall is now blocking. I've also
had a similar scenario after installing Norton Internet Security (which
strips referer headers before they're sent out), but that would normally
affect all browsers, not just IE.

If at all possible, a fix would be to use a server-side language to
explicitly write out the current document's URL in the link.

Patrick

Patrick H. Lauke
Webmaster / University of Salford
http://www.salford.ac.uk
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**




**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



RE: [WSG] W3C REFERER FIX?

2004-11-29 Thread Patrick Lauke
 From: Sam Hutchinson

 this in itself is an example of a browser/OS affecting
 accessibility.

Actually, it's a good example of something else: don't rely on any
outside data that's not under your direct control. Having a system
that purely relies on referers, and breaks down when they're not
available, is not very flexible. In terms of accessibility, it's a
prime example of what not to do (relying on referers, not the blocking
of them), as you can't guarantee that they'll be present at all...similar
to not relying on javascript etc.

 Cheers All. Will post a workaround when i've made it.

Short of changing the security settings of your machine, there's not
much you can do I think (hope, as it's been implemented for a reason,
and it would be ridiculous if web developers could simply override it).
Again, the best way is to use a server-side language and write out
the URL of the current page dynamically on the validation link's href.

Patrick

Patrick H. Lauke
Webmaster / University of Salford
http://www.salford.ac.uk
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



RE: [WSG] W3C REFERER FIX?

2004-11-29 Thread Sam Hutchinson
so I shouldn't use the W3C referer code to check my website validity?

should I be using individual URL strings to validate?

What about my dynamically created pages? I don't want to edit each
individual page in my site just to add a validity link checker?

Again, the best way is to use a server-side language and write out
the URL of the current page dynamically on the validation link's href.

Anyone out there doing this? I'd like to have a look at the code in order to
implement it.

Sam




-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Patrick Lauke
Sent: Monday, November 29, 2004 04:25
To: [EMAIL PROTECTED]
Subject: RE: [WSG] W3C REFERER FIX?


 From: Sam Hutchinson

 this in itself is an example of a browser/OS affecting
 accessibility.

Actually, it's a good example of something else: don't rely on any
outside data that's not under your direct control. Having a system
that purely relies on referers, and breaks down when they're not
available, is not very flexible. In terms of accessibility, it's a
prime example of what not to do (relying on referers, not the blocking
of them), as you can't guarantee that they'll be present at all...similar
to not relying on javascript etc.

 Cheers All. Will post a workaround when i've made it.

Short of changing the security settings of your machine, there's not
much you can do I think (hope, as it's been implemented for a reason,
and it would be ridiculous if web developers could simply override it).
Again, the best way is to use a server-side language and write out
the URL of the current page dynamically on the validation link's href.

Patrick

Patrick H. Lauke
Webmaster / University of Salford
http://www.salford.ac.uk
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**





**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



Re: [WSG] W3C REFERER FIX?

2004-11-29 Thread Mordechai Peller
Sam Hutchinson wrote:
yeah it works on my slave machine running sp1, but I tend not to have that
connected, as it will just get eaten by the web (yours is still alive?).
Besides avoiding using IE, having a good firewall helps. Personally, 
I've been happy with Sygate.
**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**


RE: [WSG] W3C REFERER FIX?

2004-11-29 Thread Patrick Lauke
At the risk of, once again, going off topic (which this whole thread
probably already is)...

 From: Sam Hutchinson

 Anyone out there doing this? I'd like to have a look at the 
 code in order to
 implement it.

To use PHP as an example
a href=http://validator.w3.org/check?amp;uri=?php echo 
$_SERVER['HTTP_HOST'].$_SERVER['REQUEST_URI']?.../a

Patrick

Patrick H. Lauke
Webmaster / University of Salford
http://www.salford.ac.uk
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



RE: [WSG] W3C REFERER FIX?

2004-11-29 Thread Peter Firminger
Hi,

 yeah it works on my slave machine running sp1, but I tend not
 to have that
 connected, as it will just get eaten by the web (yours is
 still alive?). it

The web never ate my machine pre SP2. Maybe I am more careful about where I
browse.

 looks like it is a sp2 IE thing stripping the headers out.
 amongst other
 things. this in itself is an example of a browser/OS affecting
 accessibility.

I have IE 6.02 on WinXP SP2 and it all works fine for me so please don't
jump to conclusions blaming Microsoft.

I suggest that it is a Norton AntiVirus or Norton Personal Firewall problem
(explicit but educated stab in the dark). If you are indeed running any of
the Symantec suite of products (lets call them CodeBreakers), shut them down
for a minute, reload the page and try the referrer link again.

If that doesn't work, keep looking (proxy server etc.), it ain't SP2 or I
would have the same problem.

P


**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



Re: [WSG] W3C REFERER FIX?

2004-11-29 Thread Richard Czeiger
Hi All - I've actually come across this before as well.
But for my machine, this error only happens when trying to validate pages
sitting on my hard-drive.
The link is for the form that checks online pages. Upload your page to a
server and try again  :o)

You can get heaps of bookmarklets that will help you validate your page
while in development.
These access the W3C's Validate by Upload form.

Hope this helps  :o)

Richard

**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**