Angular 2 Accessing AWS API Gateway
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Baffled on what the issue is here. I am trying to access a Lambda function on AWS through my Angular 2 application. Cross origin is enabled in AWS. In Chrome I am getting 200 responses in the Network tab.
Preflight Options Request
GET Request
The console however shows a 403
Here is the Angular code
import { HttpClient } from '@angular/common/http';
import { Observable } from 'rxjs';
getAWS(): Observable<any> {
return this.http.get('https://9rw0xrw730.execute-api.us-east-1.amazonaws.com/default/...', {
headers: {
'x-api-key': 'myapi key'
}
}
);
}
angular cors aws-api-gateway asked Nov 16 '18 at 15:40
timdw5stimdw5s
385
add a comment |
Baffled on what the issue is here. I am trying to access a Lambda function on AWS through my Angular 2 application. Cross origin is enabled in AWS. In Chrome I am getting 200 responses in the Network tab.
Preflight Options Request
GET Request
The console however shows a 403
Here is the Angular code
import { HttpClient } from '@angular/common/http';
import { Observable } from 'rxjs';
getAWS(): Observable<any> {
return this.http.get('https://9rw0xrw730.execute-api.us-east-1.amazonaws.com/default/...', {
headers: {
'x-api-key': 'myapi key'
}
}
);
}
asked Nov 16 '18 at 15:40
timdw5stimdw5s
385
1
The response headers for the GET request show that there’s no Access-Control-Allow-Origin header in the response. That is, the server is sending the Access-Control-Allow-Origin header only for the response to the preflight OPTIONS request. It needs to be configured to also send the Access-Control-Allow-Origin header for GET responses.
– sideshowbarker
Nov 16 '18 at 21:59
add a comment |
Baffled on what the issue is here. I am trying to access a Lambda function on AWS through my Angular 2 application. Cross origin is enabled in AWS. In Chrome I am getting 200 responses in the Network tab.
Preflight Options Request
GET Request
The console however shows a 403
Here is the Angular code
import { HttpClient } from '@angular/common/http';
import { Observable } from 'rxjs';
getAWS(): Observable<any> {
return this.http.get('https://9rw0xrw730.execute-api.us-east-1.amazonaws.com/default/...', {
headers: {
'x-api-key': 'myapi key'
}
}
);
}
asked Nov 16 '18 at 15:40
timdw5stimdw5s
385
Baffled on what the issue is here. I am trying to access a Lambda function on AWS through my Angular 2 application. Cross origin is enabled in AWS. In Chrome I am getting 200 responses in the Network tab.
Preflight Options Request
GET Request
The console however shows a 403
Here is the Angular code
import { HttpClient } from '@angular/common/http';
import { Observable } from 'rxjs';
getAWS(): Observable<any> {
return this.http.get('https://9rw0xrw730.execute-api.us-east-1.amazonaws.com/default/...', {
headers: {
'x-api-key': 'myapi key'
}
}
);
}
asked Nov 16 '18 at 15:40
timdw5stimdw5s
385
asked Nov 16 '18 at 15:40
timdw5stimdw5s
385
asked Nov 16 '18 at 15:40
timdw5stimdw5s
385
asked Nov 16 '18 at 15:40
timdw5stimdw5s
385
asked Nov 16 '18 at 15:40
timdw5stimdw5s
385
385
1
The response headers for the GET request show that there’s no Access-Control-Allow-Origin header in the response. That is, the server is sending the Access-Control-Allow-Origin header only for the response to the preflight OPTIONS request. It needs to be configured to also send the Access-Control-Allow-Origin header for GET responses.
– sideshowbarker
Nov 16 '18 at 21:59
add a comment |
1
The response headers for the GET request show that there’s no Access-Control-Allow-Origin header in the response. That is, the server is sending the Access-Control-Allow-Origin header only for the response to the preflight OPTIONS request. It needs to be configured to also send the Access-Control-Allow-Origin header for GET responses.
– sideshowbarker
Nov 16 '18 at 21:59
1
1
The response headers for the GET request show that there’s no Access-Control-Allow-Origin header in the response. That is, the server is sending the Access-Control-Allow-Origin header only for the response to the preflight OPTIONS request. It needs to be configured to also send the Access-Control-Allow-Origin header for GET responses.
– sideshowbarker
Nov 16 '18 at 21:59
The response headers for the GET request show that there’s no Access-Control-Allow-Origin header in the response. That is, the server is sending the Access-Control-Allow-Origin header only for the response to the preflight OPTIONS request. It needs to be configured to also send the Access-Control-Allow-Origin header for GET responses.
– sideshowbarker
Nov 16 '18 at 21:59
add a comment |
1 Answer
1
active
oldest
votes
Solved...
I had to explicitly add it to the Lambda Function itself. I did add it to the API Gateway which got me to the point above. But still didn't have the header on the actual response.
Here is the Lambda code:
answered Nov 26 '18 at 17:44
timdw5stimdw5s
385
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53341075%2fangular-2-accessing-aws-api-gateway%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Solved...
I had to explicitly add it to the Lambda Function itself. I did add it to the API Gateway which got me to the point above. But still didn't have the header on the actual response.
Here is the Lambda code:
answered Nov 26 '18 at 17:44
timdw5stimdw5s
385
add a comment |
Solved...
I had to explicitly add it to the Lambda Function itself. I did add it to the API Gateway which got me to the point above. But still didn't have the header on the actual response.
Here is the Lambda code:
answered Nov 26 '18 at 17:44
timdw5stimdw5s
385
add a comment |
Solved...
I had to explicitly add it to the Lambda Function itself. I did add it to the API Gateway which got me to the point above. But still didn't have the header on the actual response.
Here is the Lambda code:
answered Nov 26 '18 at 17:44
timdw5stimdw5s
385
Solved...
I had to explicitly add it to the Lambda Function itself. I did add it to the API Gateway which got me to the point above. But still didn't have the header on the actual response.
Here is the Lambda code:
answered Nov 26 '18 at 17:44
timdw5stimdw5s
385
answered Nov 26 '18 at 17:44
timdw5stimdw5s
385
answered Nov 26 '18 at 17:44
timdw5stimdw5s
385
answered Nov 26 '18 at 17:44
timdw5stimdw5s
385
385
add a comment |
add a comment |
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.
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%2f53341075%2fangular-2-accessing-aws-api-gateway%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
1
The response headers for the GET request show that there’s no Access-Control-Allow-Origin header in the response. That is, the server is sending the Access-Control-Allow-Origin header only for the response to the preflight OPTIONS request. It needs to be configured to also send the Access-Control-Allow-Origin header for GET responses.
– sideshowbarker
Nov 16 '18 at 21:59