[ 
https://issues.apache.org/jira/browse/RAMPART-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thilina Buddhika resolved RAMPART-305.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0

Thanks AmilaJ for the patch. 

After applying the patch, it is no longer returning the HTML error page (when 
deployed on an App Server), rather it sends the original Axis Fault. 

Patch is committed to r1072324.


> If Rampart detects a security error a HTML page is send to the client instead 
> of a SOAP fault
> ---------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-305
>                 URL: https://issues.apache.org/jira/browse/RAMPART-305
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>         Environment: Axis2-1.5..1 is installed as web app under Tomcat 5.5.28 
> and uses Rampart 1.4.
> Running on Windows XP 
>            Reporter: Herwig David
>            Assignee: Thilina Buddhika
>             Fix For: 1.6.0
>
>         Attachments: RAMPART-305.diff, WS7X4AssortmentOrder.wsdl, axis2.log, 
> request.txt, response.txt, services.xml
>
>
> If I call a web service with wrong security data rampart correctly detects 
> that 'The signature or decryption was invalid'. That's fine.
> Unfortunately I get a NullPointerException when returning to the client 
> afterwards.
> Is there a way to just send the SOAP fault back to the client instead of 
> sending a HTML page?
> Is this related to issue RAMPART-164?
> I've attached the log file, the wsdl file and messages send between client 
> and server.
> Thanks and regards,
> Herwig

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to