Home Audience Developers Cross-Origin Resource Sharing (CORS): A Primer

Cross-Origin Resource Sharing (CORS): A Primer


For security reasons, browsers restrict cross-origin HTTP requests. If the coder is not aware of this or forgets about it, it can be pretty frustrating as the required results will not be obtained. Here is an instance of such an occurrence, which the author demonstrates how to solve.

It was a lovely Sunday afternoon in Bengaluru. Unfortunately, I was stuck with my code. I had come up with an idea related to social media, and for the past few weeks, I had been coding to develop a solution for this idea. Well, this article is not to talk about that idea, which is still at a nascent stage and I wouldn’t like to share it, just yet. This write-up is to explain why I got stuck with the code and how I finally solved the problem.

First, I will need to give readers a little background. There is a profile-creation service that I have written using Spring Boot, and I have started that service on Port 8082. I have also written an Angular code snippet, through which I am consuming the service to store profile data in MongoDB. The Angular local server is running on Port 4200. A small piece of the code has been reproduced below:

addProfile service

import com.iWant.repository.Profile;



public class ProfileServiceController {


private ProfileService profileService;


//public String addProfile(@PathVariable String fname)

public ResponseEntity<Profile> addProfile(@RequestBody Profile profile)


try {


} catch (Exception e) {

// TODO Auto-generated catch block



return new ResponseEntity<Profile>(profile, HttpStatus.OK);



public Profile findName(String fname)


return this.profileService.find(fname);



Profile service

The code for the profile service is given below. The code has been written in Angular.

import { Injectable } from ‘@angular/core’;

import { HttpClient } from ‘@angular/common/http’;

import { Observable } from ‘rxjs/Observable’;

import {FriendProfile} from ‘./friend-add/friend-profile.service’;

import { RequestOptions } from ‘@angular/http’;

import { Data } from ‘@angular/router’;


export class FriendService {

fprofile: FriendProfile;

constructor(private http: HttpClient) { }

getAll(): Observable<any> {

return this.http.get(‘//localhost:8083/api/getProfile/’);


addFriend(firstName, lastName, dateOfBirth) {

this.fprofile = new FriendProfile(firstName, lastName, dateOfBirth);

const url = ‘//localhost:8082/api/addProfile/profile’;

this.http.post(url, this.fprofile)

.subscribe((data: any) => {console.log(data); });



If you look at the code above, it is pretty simple. It is calling the rest service with a post method passing a JSON object in the body. But, unfortunately, the code was not doing what it was supposed to do—which was to store the data in MongoDB. I was clueless about how to resolve this until I enabled the console and looked at the error.

And then, everything became crystal clear. This is an error due to cross-origin resource sharing (CORS). I knew about it, but it did not strike me then. I immediately went back to the services code and added the CORS annotation to get rid of this error.




public class ProfileServiceController {


private ProfileService profileService;


After solving the problem, I thought of writing this short article on CORS to share my experience with fellow developers.

What is CORS?

To understand CORS, we will need to know what the same-origin policy is. This is a security concept that blocks JavaScript code from making requests to resources in a different domain or origin. CORS, on the other hand, is a mechanism through which a JavaScript running on a Web page can consume a resource running in a different origin.

Cross-origin communication starts with a client making a GET, POST or HEAD request against a server resource. The header of the request contains the origin information of the request. The server in the other domain will inspect the origin information, and will either block or allow the request. If the request is allowed, the server will respond with the requested resource and an ‘Access-Control-Allowed-Origin’ header in the response. The browser allows the request if the origin of the request matches with the ‘Access-Control-Allowed-Origin’ header. The Access-Control-Allowed-Origin can be set to a list of allowed requestors or it may also be set to ‘*’. If it is set to the latter, it means that clients of any origin are allowed, which is not a best practice from the security point of view.

However, if an API is public, it makes sense to set it to ‘*’. In Spring Boot, we have an easy way to set it up through the CORS annotation, as mentioned earlier.



Please enter your comment!
Please enter your name here

Exit mobile version