Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Handling errors from legacy cgi links



On Wed, 28 Mar 2007 18:07:22, Dan Shoop wrote:
> At 5:20 PM -0400 3/28/07, Jason Deraleau wrote:
>>On Mar 28, 2007, at 4:41 PM, Jonathan Schwartz wrote:
>>
>>>This is by bad.  I must not have explained this properly.
>>>
>>
>>Don't mind Dan's response. The situation you presented was a little
>>difficult to follow, but Dan lacks the tact to solicit information
>>in a manner that isn't mildly insulting. Search the list archives if
>>you need more examples, but please don't take it personally.
>
> Ask the wrong question, get the wrong answer.
>
>>>Phew!  That being re-stated, how do I trap these "Forbidden" errors
>>>and gracefully deliver users to a more informative error handling
>>>page.
>>>
>>
>>One thing you might consider is using Apache's built-in facilities
>>to redirect the old URL to the new URL for that service. This is a
>>bit of an advanced configuration, but it is a great way to provide
>>the experience you desire and to delve a bit more into the software
>>that provides web services on Mac OS X Server. Here's a link to an
>>article on the topic:
>>
>><http://httpd.apache.org/docs/2.0/misc/rewriteguide.html>http://httpd.apache.org/docs/2.0/misc/rewriteguide.html
>
> This is a lot of overhead for this. The Apache phases of operation
> trap errors very efficiently. You should use those methods rather
> than the ham handed redirects.
>
>>This is a graceful way to solve the problem in a way that is
>>essentially transparent to your users. While it won't do anything
>>like force their browser bookmarks to be updated, it will still get
>>them to the page they expect.
>
> That's a bad practice since you'll need to keep doing this forever.
> Better to encourage them to use (and rebookmark) the correct page and
> reduce your server overhead.

It's unclear what Jason meant by "transparent to your users".  Apache can
handle it internally (i.e. serve new.php instead of old.cgi) or send a
redirect (i.e. respond with a 3xx code).  The first approach is truly
transparent, while the second approach is handled by the web browser
"transparently" (i.e. it automatically requests the correct document).  If
you send a redirect, then newly-created bookmarks will be correct.

> But it is YAWTDI.
>
> --
>
> -dhan
>

-- 
Patrick Schwisow
Web Information Manager
Waukegan Public School District 60
http://www.waukeganschools.org/

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden

This email sent to email@hidden



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.