AbortScript could serve several different reasons for interrupting processing depending on the result returned by [::rivet::abort_code]. I will leave it without argument because it's harmless, but it could be a good reason for thinking of a 'rivet scheme' for encoding these exceptions in the abort_page argument. They can get the URL from Location but they need to know why execution got there in the first place
-- M On 12/15/2014 10:20 PM, Damon Courtney wrote: > I would just abort with “redirect”. If they want the location, they can call > [headers set Location] to get it. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
