javascript - CORS angular js + restEasy on POST - Stack Overflow

admin管理员组

文章数量:1336139

I'm doing some POST requests from my angular js app to my RESTful API implemented using RestEasy.
The case is that I need CORS so I added a servlet filter with this code:

public void doFilter(ServletRequest req, ServletResponse res, FilterChain chain) throws IOException, ServletException {
    HttpServletResponse response = (HttpServletResponse) res;
    response.addHeader("Access-Control-Allow-Origin", "*");
    response.addHeader("Access-Control-Allow-Methods", "POST, GET, OPTIONS, DELETE");
    response.addHeader("Access-Control-Max-Age", "3600");
    response.addHeader("Access-Control-Allow-Headers", "Content-Type");
    chain.doFilter(req, res);
}

But I can't figure out why it works only with GET requests and not POST requests, the error on chrome's console is:

No 'Access-Control-Allow-Origin' header is present on the requested resource

My POST request is:

$http({method: 'POST', 
       url: myUrl,
       data: $scope.data,
       headers: {'Content-Type': 'application/json'}
});  

This is the reponse I receive on POST:

Allow:POST, OPTIONS
Content-Length:0
Date:Thu, 03 Apr 2014 23:27:22 GMT
Server:Apache-Coyote/1.1

Any Idea? Thanks!
EDIT:
Tested on IE10 and it works but doesn't work on chrome neither firefox ... any body knows why?

I'm doing some POST requests from my angular js app to my RESTful API implemented using RestEasy.
The case is that I need CORS so I added a servlet filter with this code:

public void doFilter(ServletRequest req, ServletResponse res, FilterChain chain) throws IOException, ServletException {
    HttpServletResponse response = (HttpServletResponse) res;
    response.addHeader("Access-Control-Allow-Origin", "*");
    response.addHeader("Access-Control-Allow-Methods", "POST, GET, OPTIONS, DELETE");
    response.addHeader("Access-Control-Max-Age", "3600");
    response.addHeader("Access-Control-Allow-Headers", "Content-Type");
    chain.doFilter(req, res);
}

But I can't figure out why it works only with GET requests and not POST requests, the error on chrome's console is:

No 'Access-Control-Allow-Origin' header is present on the requested resource

My POST request is:

$http({method: 'POST', 
       url: myUrl,
       data: $scope.data,
       headers: {'Content-Type': 'application/json'}
});  

This is the reponse I receive on POST:

Allow:POST, OPTIONS
Content-Length:0
Date:Thu, 03 Apr 2014 23:27:22 GMT
Server:Apache-Coyote/1.1

Any Idea? Thanks!
EDIT:
Tested on IE10 and it works but doesn't work on chrome neither firefox ... any body knows why?

• javascript
• angularjs
• resteasy

Share Improve this question Follow edited Apr 4, 2014 at 1:29 Adnane.T asked Apr 3, 2014 at 22:10 Adnane.TAdnane.T 27211 gold badge44 silver badges1313 bronze badges 16

• how are you requesting with GET? – Eliran Malka Commented Apr 3, 2014 at 23:14
• the same way but with 'GET' instead of 'POST' and another url but on the same WS – Adnane.T Commented Apr 3, 2014 at 23:24
• i don't think you need to explicitly allow the Content-Type header. try and remove that. – Eliran Malka Commented Apr 3, 2014 at 23:47
• still doesn't work, as you see in my edit, it seems that its browser thing ... FF and chrome doesn't receive the same response headers as IE – Adnane.T Commented Apr 3, 2014 at 23:48
• works on IE but not on Chrome or Firefox? that's odd. – Eliran Malka Commented Apr 4, 2014 at 0:03

 |  Show 11 more ments

2 Answers 2

Sorted by: Reset to default 1

Well finally I came to this workaround:
The reason it worked with IE is because IE sends directly a POST instead of first a preflight request to ask for permission.
But I still don't know why the filter wasn't able to manage an OPTIONS request and sends by default headers that aren't described in the filter (seems like an override for that only case ... maybe a restEasy thing ...)

So I created an OPTIONS path in my rest service that rewrites the reponse and includes the headers in the response using response header

I'm still looking for the clean way to do it if anybody faced this before.

I have had good luck configuring Cross-origin resource sharing (CORS) for my API (on Wildfly) by using this lib:

<dependency>
<groupId>.thetransactionpany</groupId>
<artifactId>cors-filter</artifactId>
<version>2.1</version>
</dependency>

It's very easy to setup. Just add the above dependency to your pom and then add the following config to the webapp section of your web.xml file.

<filter>
    <filter-name>CORS</filter-name>
    <filter-class>.thetransactionpany.cors.CORSFilter</filter-class>

    <init-param>
        <param-name>cors.allowGenericHttpRequests</param-name>
        <param-value>true</param-value>
    </init-param>

    <init-param>
        <param-name>cors.allowOrigin</param-name>
        <param-value>*</param-value>
    </init-param>

    <init-param>
        <param-name>cors.allowSubdomains</param-name>
        <param-value>false</param-value>
    </init-param>

    <init-param>
        <param-name>cors.supportedMethods</param-name>
        <param-value>GET, HEAD, POST, DELETE, OPTIONS</param-value>
    </init-param>

    <init-param>
        <param-name>cors.supportedHeaders</param-name>
        <param-value>*</param-value>
    </init-param>

    <init-param>
        <param-name>cors.supportsCredentials</param-name>
        <param-value>true</param-value>
    </init-param>

    <init-param>
        <param-name>cors.maxAge</param-name>
        <param-value>3600</param-value>
    </init-param>

</filter>

<filter-mapping>
    <!-- CORS Filter mapping -->
    <filter-name>CORS</filter-name>
    <url-pattern>*</url-pattern>
</filter-mapping>

You can also configure it with a properties file instead if you prefer. This lib works like a charm and gives you a lot of configuration flexibility!

本文标签： javascriptCORS angular jsrestEasy on POSTStack Overflow