WSO2 EI/ESB Change Backend Response Status Code

With WSO2 Enterprise Integrator or Enterprise Service Bus servers, if you want to change the backend server response code, you can set custom status status code as below:

 <property name="HTTP_SC" scope="axis2" type="STRING" value="403"/>

If you are getting 'HTTP/1.1 202 Accepted' response from your backend, you need to set "SC_ACCEPTED" as false by setting a custom SC_ACCEPTED

Ex:  Receiving 202 from backend and change it to 200

<filter regex="202" source="$axis2:HTTP_SC">
        <then>
            <property action="remove" name="HTTP_SC" scope="axis2"/>
            <property name="SC_ACCEPTED" scope="axis2" value="false"/>
            <property name="HTTP_SC" scope="axis2" type="STRING" value="200"/>
        </then>
        <else/>
    </filter>


Comments

Post a Comment

Popular posts from this blog

Building a RESTFul Service using Spring Boot

Image
Everyone is talking about Microservices such as WSO2 Microservice Framework , Spring Boot , etc. Since I haven't worked on any Spring related project since a very long time, I thought to implement a simple RESTFul service using Spring Boot. So I started with Spring documentation. It is straightforward.  You can create the structure of your project using " Spring Initializr ". This is an online tool where you can add all the desired dependencies to your project POM file. Since I am a big fan of Maven, I am generating a maven project. In the Spring Initializr UI, you can choose the Language, Spring Boot Version, Project Group ID, artifact name, etc. Please refer below screenshot for information I have provided while generating the project. When clicking on "Generate Project", it will download zipped maven project into your computer. Unzip it and import into an IDE. The initial project structure is like below. In my HelloWorld REST service impleme
Read more

Integrating Swagger with Spring Boot REST API

Image
In the last post, I talked about my experience with creating RESTFul Services using Spring Boot . When creating a REST API, proper documentation is a mandatory part of it. What is Swagger? Swagger (Swagger 2) is a specification for describing and documenting a REST API. It specifies the format of the REST web services including URL, Resources, methods, etc. Swagger will generate documentation from the application code and handle the rendering part as well. In this post, I am going to integrate Swagger 2 documentation into a Spring Boot based REST web service. So I am going to use Springfox implementation to generate the swagger documentation. If you want to know how to run/build Spring Boot project, please refer my previous post. Springfox provides two dependencies to generate API Doc and Swagger UI. If you are not expecting to integrate Swagger UI into your API level, no need to add  Swagger UI dependency. <dependency>     <groupId>io.springfox</groupId>
Read more

Secure Spring Boot REST API using Basic Authentication

This is the third post of my Spring Boot Blog post series. In the very first post, I talked about my experience with creating RESTFul Services using Spring Boot. Then I have expanded the sample to integrate with Swagger documentation. In this post, I am going to expand above sample with security aspect. What is API Security API Security is a wide area with many different definitions, meanings, and solutions. The main key terms in API security are Authorization, Authentication, Encryption, Federation, and Delegation. However, I am not going to talk about each of them here. What is Authentication Authentication is used to reliably determine the identity of an end user and give access to the resources based on the correctly identified user. What is Basic Authentication Basic Authentication is the simplest way to enforce access controling to resources. Here, the HTTP user agent provides the username and the password when making a request. The string containing the username and
Read more