how to byPass json custom error response code

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

how to byPass json custom error response code

Eddy Wiyatno

All,

 

I need help, how to configure apache to make bypass json custom error response code. If “proxyerroroverride off” it is successful. But if “On” it is not successful, it is direct to default 500 html error code by apache. But I need proxyerroroverride is On for direct to my own html custom error response code for 2xx and 4xx.

 

Thank you

Eddy



Privileged/confidential information may be contained in this message. If you are not the named recipient or addressee, you are hereby notified that any use review, disclosure or copying of the contents herein is strictly prohibited. In such a case, kindly discard all its contents and notify sender accordingly regarding such unauthorized disclosure or transmission by email. Opinions, conclusions, statements and other information in this message that do not relate to the official business of CIMB Group shall be understood as neither given or endorsed by it. The contents herein are meant strictly for the use of the named recipient or addressee of CIMB Group. No assumption of responsibility or liability whatsoever is undertaken by CIMB Group in respect of prohibited and unauthorised use by any other person.
Reply | Threaded
Open this post in threaded view
|

how to byPass json custom error response code

Eddy Wiyatno

All,

 

I need help, how to configure apache to make bypass json custom error response code. If “proxyerroroverride off” it is successful. But if “On” it is not successful, it is direct to default 500 html error code by apache. But I need proxyerroroverride is On for direct to my own html custom error response code for 2xx and 4xx.

 

Thank you

Eddy

 



Privileged/confidential information may be contained in this message. If you are not the named recipient or addressee, you are hereby notified that any use review, disclosure or copying of the contents herein is strictly prohibited. In such a case, kindly discard all its contents and notify sender accordingly regarding such unauthorized disclosure or transmission by email. Opinions, conclusions, statements and other information in this message that do not relate to the official business of CIMB Group shall be understood as neither given or endorsed by it. The contents herein are meant strictly for the use of the named recipient or addressee of CIMB Group. No assumption of responsibility or liability whatsoever is undertaken by CIMB Group in respect of prohibited and unauthorised use by any other person.