Using header("Locatio n:...". How to pass over array variable?

[Dave Smithz]

Hi there,

I have a php script that does some form input validation. As it verifies
each field if the field has incorrect data, it appends an error message to
an $error array. E.g.

if (an_error = true) {
$errors.="<tr>< td>You have note entered a surname. This is mandatory date
of birth incorrectly.</td></tr>";
}

Previously I had always had the HTML error page code contained within the
same script, but now I am moving it out to make maintenance easier.

When validation completes there is now a statement that says
if ($errors!="") {
header("Locatio n: ./error_page.php" );
}

However, how can I pass the errors array to the error_page. I want to be
able to list each error individually.

Forgive me if this is a silly easy question. I have only been doing PHP for
about a week.
Thanks in advance.

Kind regards

Dave

[Chris Hope]

Michael Fesser wrote:

As I was told in this very group some weeks back (by you. :P) a
locationheader needs an absolute URL.

No, it doesn't.

It does.

RFC 2616, section 14.30

And section 5 and the following subsections of RFC3986 deal with the
resolution of relative URIs. However, it was only published in January
2005 but I'm pretty sure all the browsers I have ever used since 1997
have supported relative URI redirection.

It is still probably best to have full URIs though, and it's easy enough
to do using the $_SERVER['HTTP_HOST'] variable in your location string.

--
Chris Hope - The Electric Toolbox - http://www.electrictoolbox.com/

[Michael Fesser]

.oO(Chris Hope)

Michael Fesser wrote:

RFC 2616, section 14.30
And section 5 and the following subsections of RFC3986 deal with the
resolution of relative URIs. However, it was only published in January
2005 but I'm pretty sure all the browsers I have ever used since 1997
have supported relative URI redirection.

The HTTP RFC clearly states that the Location URI has to be absolute.
IMHO a conforming user agent doesn't have to be able to resolve relative
URIs if he can expect an absolute one.
It is still probably best to have full URIs though, and it's easy enough
to do using the $_SERVER['HTTP_HOST'] variable in your location string.

Agreed.

Micha

[John Dunlop]

Tim Van Wassenhove wrote:

[Erwin Moller wrote:]

micha wrote:

header("Locatio n: ./error_page.php? NAME=VALUE")

As I was told in this very group some weeks back (by you. :P)
One of us is getting our Michas confused!
a locationheader needs an absolute URL.

Quite true here.
But now we have:
http://www.ietf.org/rfc/rfc3986.txt

But that doesn't change RFC2616, which requires that HTTP
Location headers consist of a single absolute URI. HTTP/1.1
delegates the definition of 'absoluteURI' to RFC2396, now
obsoleted by RFC3986. By looking at Appendix D.2 of the new
RFC, you can see that the 'absoluteURI' rule from RFC2396 is
equivalent to the 'absolute-URI' rule of RFC3986. The only
real difference I spotted between the two is that now the
path component can be empty.

http://www.ietf.org/rfc/rfc2396.txt
http://www.ietf.org/rfc/rfc3986.txt

Mind you, that's all a bit irrelevant. The HTTP/1.1 errata
corrects the definition of Location by allowing a fragment
identifier, and provides a new ABNF rule:

Location = "Location" ":" absoluteURI [ "#" fragment ]

http://skrb.org/ietf/http_errata.htm...tion-fragments

So, to sum up, under the new RFC3986 and by taking into
account the HTTP/1.1 errata, an HTTP Location header
effectively consists of a single *URI*:

URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ]

--
Jock

[Anonymous]

Michael Fesser wrote:

.oO(Anonymous)

Erwin Moller wrote:

As I was told in this very group some weeks back (by you. :P) a
locationheader needs an absolute URL.

No, it doesn't.

It does.

RFC 2616, section 14.30

[readin it up]

Interesting. You are right, according to the RFC it does.

It also works relative, however.