Jetty Logo
Version: 9.2.3.v20140905
Contact the core Jetty developers at www.webtide.com

private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery

Cross Origin Filter

Info
Usage
Setup
Configuration

Info

Usage

HTTP requests made from a script are subject to well known restrictions, the most prominent being the same domain policy.

Firefox 3.5 introduced support for W3C's Access Control for Cross-Site Requests specification, which requires a compliant client (for example, Firefox 3.5) and a compliant server (via this servlet filter).

This filter implements the required bits to support the server-side contract of the specification, and will allow a compliant client to perform cross-domain requests via the standard XMLHttpRequest object. If the client does not issue a compliant cross-domain request, this filter does nothing, and its overhead is the check of the presence of the cross-domain HTTP header.

This is extremely useful in CometD web applications where it is now possible to perform cross-domain long polling without using script injection (also known as the JSONP transport), and therefore removing all the downsides that the JSONP transport has (it's chattier, does not react quickly to failures, has a message size limit, uses GET instead of POST, etc.).

Setup

You will need to put the jetty-servlets.jar file onto your classpath. If you are creating a webapp, ensure that this jar is included in your webapp's WEB-INF/lib. Or, if you are running jetty embedded you will need to ensure that jetty-servlets.jar is on the execution classpath. You can download the jetty-servlets.jar from the Maven Central Repository at http://central.maven.org/maven2/org/eclipse/jetty/jetty-servlets/.

Configuration

This is a regular servlet filter that must be configured in web.xml.

It supports the following configuration parameters:

allowedOrigins

a comma separated list of origins that are allowed to access the resources. Default value is: * (all origins)

allowedMethods

a comma separated list of HTTP methods that are allowed to be used when accessing the resources. Default value is: GET,POST,HEAD

allowedHeaders

a comma separated list of HTTP headers that are allowed to be specified when accessing the resources. Default value is: X-Requested-With,Content-Type,Accept,Origin

preflightMaxAge

the number of seconds that preflight requests can be cached by the client. Default value is 1800 seconds (30 minutes)

allowCredentials

a boolean indicating if the resource allows requests with credentials. Default value is: true

preflightMaxAge

the number of seconds that preflight requests can be cached by the client. Default value is 1800 seconds (30 minutes)

chainPreflight

if true preflight requests are chained to their target resource for normal handling (as an OPTION request). Otherwise the filter will response to the preflight. Default is true.

exposedHeaders

a comma separated list of HTTP headers that are allowed to be exposed on the client. Default value is the empty list.

A typical configuration could be:

See an error or something missing? Contribute to this documentation at Github!(Generated: 2014-11-28T01:00:28-08:00)