[Bug 1155] 404, 403, 401, 500, etc. Error pages

http://bugs.xaraya.com/show_bug.cgi?id=1155





------- Comment #11 from [email protected]  2009-07-08 20:36 GMT -------
1 more additional file change for those that want to attempt to tweak the
system;
This one is to Stop the Redirect and inserting the data into URL
(WARNING: No idea what additional consequences may occur from this change!)
--------------------------------------------------

File:  xarException.php
Location:  /includes/xarException.php
Add:  N/A (see Original + Replacement)
Line:  607(ish)
After: after:   // CHECKME: <mrb> This introduces a dependency to 2 subsystems

Original:
        xarResponseRedirect(xarModURL('base','user','systemexit',
        array('code' => $errorType,
              'exception' => $msg,
              'product' => $product,
              'component' => $component)));
Replacement:
                // AUTOCRAT :: To Redirect on certain errors! (commented out
Redirect)
                // AUTOCRAT :: To stop DB Error getting crawled/cached - send
503
                header('HTTP/1.1 503 Service Unavailable');
                // End AUTOCRAT
                /*
        xarResponseRedirect(xarModURL('base','user','systemexit',
        array('code' => $errorType,
              'exception' => $msg,
              'product' => $product,
              'component' => $component)));
                */

--------------------------------------------------

AGain - WARNING - I do not know what additional things may be affected.
What I do see is that it instead does attempt to render to an Error Template
(message-systemerror.xd).
I understand that the Redirect is in place incase Rendering fails.
Thus the inclussion of the 503 response in the code above - rather than relying
on the Template to correctly render/produce.


-- 
Configure bugmail: http://bugs.xaraya.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

---- ** IMPORTANT ** READ BELOW ** ----
[Clip Me Start]
--------------------------------------------------------------------------
If you wish, you can reply to this message directly **however**, make sure
to use the "Reply To All" feature of your client **and** ensure that the 
bug specifier is in the subject (ie: [Bug ####]). Also, you _MUST_ have 
you're From or Reply-To address set to the same address you use to log
into your bugzilla account or your reply will not be attached to the bug.
--------------------------------------------------------------------------
[Clip Me End]