Book Image

CORS Essentials

By : Rajesh Gunasundaram
Book Image

CORS Essentials

By: Rajesh Gunasundaram

Overview of this book

This book explains how to use CORS, including specific implementations for platforms such as Drupal, WordPress, IIS Server, ASP.NET, JBoss, Windows Azure, and Salesforce, as well as how to use CORS in the Cloud on Amazon AWS, YouTube, Mulesoft, and others. It examines limitations, security risks, and alternatives to CORS. It explores the W3C Specification and major developer documentation sources about CORS. It attempts to predict what kinds of extension to the CORS specification, or completely new techniques, will come in the future to address the limitations of CORS Web developers will learn how to share code and assets across domains with CORS. They will learn a variety of techniques that are rather similar in their method and syntax. The book is organized by similar types of framework and application, so it can be used as a reference. Developers will learn about special cases, such as when a proxy is necessary. And they will learn about some alternative techniques that achieve similar goals, and when they may be preferable to using CORS
Table of Contents (15 chapters)
CORS Essentials
Credits
About the Authors
www.PacktPub.com
Customer Feedback
Preface
Index

CORS in IBM Cloudant


IBM Cloudant is a NoSQL JSON document store that is optimized for handling heavy workloads of concurrent reads and writes in the cloud; a workload that is typical of large, fast-growing web and mobile apps. It provides a simple JSON API for configuring CORS for your database, which may be changed dynamically.

How to GET or PUT a CORS configuration in IBM Cloudant

IBM Cloudant provides the endpoint /_api/v2/user/config/cors. A GET call to the endpoint retrieves the CORS configuration for your application. You can change the CORS configuration with a PUT call to the endpoint.

How to GET a CORS Configuration

The following request reads the CORS configuration. Note that both localdomain.com and www.localdomain.com are allowed origins, since they are considered different domains under the same origin policy. This example also allows requests only from domains on HTTPS secured with SSL; you may allow a domain over HTTP, understanding the risk:

GET /_api/v2/user/config/cors HTTP...