On 15/01/2008, Keryx Web [EMAIL PROTECTED] wrote:
I know Opera have E4X in the works at some level
http://www.codingforums.com/showpost.php?s=a9dfc400dfd427203a99487bd4ea29d9p=448007postcount=10
That comment's based on the the fact that Opera resolved my RFE for
for each looping as fixed, and
Hi Martin and others,
On 19/1/08 1:45 AM, Martin Heiden wrote:
2. HTTP-Header Referrer - may be supressed by proxies/firewalls or the user
You can access it via (PHP|Java|ASP|...) or by JS document.referrer
Just out of interest, what happens when HTTP-Header Referrer is suppressed?
Does
Sarah Peeke wrote:
Hi Martin and others,
On 19/1/08 1:45 AM, Martin Heiden wrote:
2. HTTP-Header Referrer - may be supressed by proxies/firewalls or the
user
You can access it via (PHP|Java|ASP|...) or by JS document.referrer
Just out of interest, what happens when HTTP-Header
Chris Knowles wrote:
Sarah Peeke wrote:
Hi Martin and others,
On 19/1/08 1:45 AM, Martin Heiden wrote:
2. HTTP-Header Referrer - may be supressed by proxies/firewalls or the
user
You can access it via (PHP|Java|ASP|...) or by JS document.referrer
Just out of interest, what happens when
On 22/1/08 1:37 PM, Chris Knowles wrote:
Referer is just one HTTP header - it is separate from response codes
(200, 404 etc) and other headers. No error is thrown if it's not present
so content is passed on as normal. But because HTTP headers can be
changed along the response chain from server
On Jan 22, 2008 3:58 PM, Sarah Peeke [EMAIL PROTECTED] wrote:
So, if the HTTP headers are changed along the response chain from
server to client what is the likely outcome? Where would the user be
directed in this case?
That depends on the application. It's not a required field, but that
On Tue, 22 Jan 2008 13:58:52 +1100, Sarah Peeke wrote:
So, if the HTTP headers are changed along the response chain from
server to client what is the likely outcome? Where would the user be
directed in this case?
HTML doesn't care.
Its possible to write server-side code that generates
changed along the response chain from server to client they can't be
relied upon.
Other way 'round.
Referer is a Request header, (optionally) originated by the client.
But even user agents that provide one may have it stripped from the
Request by personal fire walls, proxies, etc.
But since
Sarah Peeke wrote:
So, if the HTTP headers are changed along the response chain from
server to client what is the likely outcome? Where would the user be
directed in this case?
The user is not directed anywhere, it's just that - in the case we're
discussing - the receiving page can't
