Re: "False" call to handleSessionRestorationErrorInContext when having a relative reference to an image
Re: "False" call to handleSessionRestorationErrorInContext when having a relative reference to an image
- Subject: Re: "False" call to handleSessionRestorationErrorInContext when having a relative reference to an image
- From: Kaj Hejer <email@hidden>
- Date: Wed, 30 Mar 2005 22:21:11 +0200
On 30. mar 2005, at 22.17, Chuck Hill wrote:
Sounds resonable (as you always do ;-)
Tell that to my wife! :-P
:) Feel free to forward my previous email to her!
But how should I know when to return a 404 response? I could look for
"nettlogg.woa/wo/*.gif" in the request url and then I know I should
return status 404. Does that sound like a resonable way of knowing
when to return status 404?
That is roughly what I was thinking. You could probably just reject
any URL ending in .gif, .jpg, .jpeg etc. etc. Another way to do this
is to compare to a correctly formed URL: nettlogg.woa/wo/<context
ID>.<element ID>.
Context ID should be one or more digits, element ID is more variable.
It should be easy to look for <digits>. after any /wo/ in a URL with
regex.
Thank you!!
-Kaj :)
Attachment:
PGP.sig
Description: This is a digitally signed message part
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden