niraj choubey
1 min readNov 6, 2019

--

Thanks Marco Faustinelli

There are two scenarios when browsers generally reject the response for “credentialed” ( withCredential =true ) request

  1. If the response does not contain a Access-Control-Allow-Credential : true header, then browser will reject the response and it will not be available to the invoking request.
  2. In a case when response does contain Access-Control-Allow-Credential : true header, browser will reject the response if Access-Control-Allow-Origin is set to wildcard “*”.

Response to a credentialed request would only be processed if response contains Access-Control-Allow-Origin value as the requesting origin along with the Access-Control-Allow-Credential : true.

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

--

--

niraj choubey
niraj choubey

Written by niraj choubey

Security professional. Aspiring to learn all security. Always ready to contribute back to the community. Passionate about writing on security.

No responses yet

Write a response