The HTTP/1.1 spec specifies that the Location: header contains an absolute URI, not a relative one, although many browsers will work with relative URIs anyway. Maybe if you provided some real information (such as what kind of error you are getting that makes you think it's invalid) you might get more help.
| We're not surrounded, we're in a target-rich environment! |
|---|
| [reply] |
Also, location header can't be sent with a Set-Cookie header. I'm pretty certain that Location is a stand alone header (sorry, can't confirm, my bibles are at work :) and that if you set it, most other headers are ignored or invalid.
.02
cLive ;-)
| [reply] |