external service dosn't store cookie
up vote
0
down vote
favorite
I'm developing a new service to hold our basket logic on a e-commerce site.
Locally we've got local.site.com which is the main site with the products etc. And we've got localhost:3000 which is the checkout flow AND the basket api (get basket, add to basket etc.)
If i press "add to basket" on local.site.com it fires a request to localhost:3000, adds the product to the basket and gets a basketId set on the cookie on the response.
No cookie is stored, which means next time i add to basket i do not get the same basket with the additional product, i get a new basket. - the basket service can't have any state with the client.
If i post to basketservice from swagger / postman everything works fine, so the endpoint is OK.
the communication between two different sites is the issue. How to solve this?
ajax request cross-domain frontend
add a comment |
up vote
0
down vote
favorite
I'm developing a new service to hold our basket logic on a e-commerce site.
Locally we've got local.site.com which is the main site with the products etc. And we've got localhost:3000 which is the checkout flow AND the basket api (get basket, add to basket etc.)
If i press "add to basket" on local.site.com it fires a request to localhost:3000, adds the product to the basket and gets a basketId set on the cookie on the response.
No cookie is stored, which means next time i add to basket i do not get the same basket with the additional product, i get a new basket. - the basket service can't have any state with the client.
If i post to basketservice from swagger / postman everything works fine, so the endpoint is OK.
the communication between two different sites is the issue. How to solve this?
ajax request cross-domain frontend
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm developing a new service to hold our basket logic on a e-commerce site.
Locally we've got local.site.com which is the main site with the products etc. And we've got localhost:3000 which is the checkout flow AND the basket api (get basket, add to basket etc.)
If i press "add to basket" on local.site.com it fires a request to localhost:3000, adds the product to the basket and gets a basketId set on the cookie on the response.
No cookie is stored, which means next time i add to basket i do not get the same basket with the additional product, i get a new basket. - the basket service can't have any state with the client.
If i post to basketservice from swagger / postman everything works fine, so the endpoint is OK.
the communication between two different sites is the issue. How to solve this?
ajax request cross-domain frontend
I'm developing a new service to hold our basket logic on a e-commerce site.
Locally we've got local.site.com which is the main site with the products etc. And we've got localhost:3000 which is the checkout flow AND the basket api (get basket, add to basket etc.)
If i press "add to basket" on local.site.com it fires a request to localhost:3000, adds the product to the basket and gets a basketId set on the cookie on the response.
No cookie is stored, which means next time i add to basket i do not get the same basket with the additional product, i get a new basket. - the basket service can't have any state with the client.
If i post to basketservice from swagger / postman everything works fine, so the endpoint is OK.
the communication between two different sites is the issue. How to solve this?
ajax request cross-domain frontend
ajax request cross-domain frontend
edited Nov 21 at 11:43
sideshowbarker
30.1k136988
30.1k136988
asked Nov 21 at 11:31
Niclas Schumacher
3819
3819
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53411171%2fexternal-service-dosnt-store-cookie%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown