blocks|key|4408201|text|您确定API终结点返回302吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4408202|确保没有为您的方法定义除302之外的任何2xx或3xx响应代码。您只能有一个“成功”的响应代码映射。2xx和3xx代码都被认为是成功代码。|4408203|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Are you sure the API endpoint is returning 302? 

Make sure you don't have any 2xx or 3xx response codes other than 302 defined for your method. You can only have one "successful" response code mapping. 2xx and 3xx codes are all considered success codes.

blocks|key|4408256|text|好了，我找到问题了。我存储位置的变量被定义为字符串而不是对象，这就是为什么网页将其显示为文本的原因。它现在正在重定向到该页面。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4408257|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Ok, I found the problem. The variable I was storing the location to is defined as a string instead of an object which is why, the web page is showing it as text. It is now redirecting to the page.

blocks|key|4408285|text|首先，您需要为"location“头创建一个方法响应。然后，您希望从Lambda的响应中映射location标头值。在Node.js运行时，您可以将其映射到integration.response.body.errorType。这样，您就可以通过执行以下操作来重定向：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4408286|//+Returns+302+or+301
var+err+=+new+Error("HandlerDemo.ResponseFound+Redirection:+Resource+found+elsewhere");
err.name+=+"http://a-different-uri";
context.done(err,+{});|code-block|syntax|javascript|4408287|有关完整的编写，请参阅：https://aws.amazon.com/blogs/compute/redirection-in-a-serverless-api-with-aws-lambda-and-amazon-api-gateway/|4408288|entityMap|0|LINK|mutability|MUTABLE|url|https://aws.amazon.com/blogs/compute/redirection-in-a-serverless-api-with-aws-lambda-and-amazon-api-gateway/^0|26|Z|0|0|C|30|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

Firstly, you want to create a method response for the "location" header. Then you'd like to map the location header value from the response of your Lambda. In Node.js runtime you could map it to <code>integration.response.body.errorType</code>. This way you'll be able to redirect by doing:

<pre><code>// Returns 302 or 301
var err = new Error("HandlerDemo.ResponseFound Redirection: Resource found elsewhere");
err.name = "http://a-different-uri";
context.done(err, {});
</code></pre>

For the full writeup, see: <a href="https://aws.amazon.com/blogs/compute/redirection-in-a-serverless-api-with-aws-lambda-and-amazon-api-gateway/" rel="nofollow">https://aws.amazon.com/blogs/compute/redirection-in-a-serverless-api-with-aws-lambda-and-amazon-api-gateway/</a>

blocks|key|4408537|text|对于使用API网关的Lambda重定向，有一个更简单的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4408538|module.exports.handler+=+(event,+context,+callback)+=>+Promise.resolve(event)
++//+.then(doStuffWithTheEventObject)
++.then(()+=>+callback(null,+{
++++statusCode:+302,
++++headers:+{
++++++Location:+'https://gohere.com',
++++},
++}))+//+Success!
++.catch(callback);+//+Fail+function+with+error|code-block|syntax|javascript|4408539|此示例来自https://blog.rowanudell.com/redirects-in-serverless/|offset|length|4408540|entityMap|0|LINK|mutability|MUTABLE|url|https://blog.rowanudell.com/redirects-in-serverless/^0|0|0|5|1G|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

There is a simpler way for Lambda redirects with API Gateway:

<pre class="lang-js prettyprint-override"><code>module.exports.handler = (event, context, callback) =&gt; Promise.resolve(event)
 // .then(doStuffWithTheEventObject)
 .then(() =&gt; callback(null, {
 statusCode: 302,
 headers: {
 Location: 'https://gohere.com',
 },
 })) // Success!
 .catch(callback); // Fail function with error
</code></pre>

This example is from <a href="https://blog.rowanudell.com/redirects-in-serverless/" rel="noreferrer">https://blog.rowanudell.com/redirects-in-serverless/</a>

blocks|key|4408479|text|这是我在Lambda中实际使用的。我把API放在一边。API收集发送给它的数据:表单数据。这是一段非常简单的代码，你可以用它做很多事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4408480|我在lambda中处理表单数据:提取变量，重新验证它们，将它们保存到dynamoDB中，然后发出一封电子邮件，要求新注册人员验证他们满足GDPR的意图，并确保我从有能力和有兴趣进行交互的人那里捕获了一个真实的电子邮件地址，然后提供屏幕上的响应。|4408481|屏幕上的响应是重定向到特定的感谢页面，解释他们需要查看电子邮件并单击链接。|4408482|在这个例子中，你所需要做的就是为你的登录页面切换Amazon.com。|4408483|通过使用变量:+redirectURL，我可以改变响应，并为不同网站页面上的一系列不同表单使用API和Lambda。如果我愿意，我可以将重定向设置为表单本身中的隐藏表单域。|4408484|​|4408485|++++let+redirectURL=+'https://amazon.com/';
++++var+response+=+{
++++++++"statusCode":+302,
++++++++"headers":+{
++++++++++++Location:+redirectURL,
++++++++}
++++};
++++callback(null,+response);|code-block|syntax|javascript|4408486|4408487|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|Z|8|@]|9|@]|A|$O|P]]|$1|Q|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|S|$]]

Here is what I actually used in my Lambda. I let the API well alone. The API collects data sent to it: form data. It is a very simple bit of code that you can do a lot with.

I process the form data in lambda: extract variables, revalidate them, save them into dynamoDB, then issue an email asking the new signup to verify their intentions to satisfy GDPR and make sure I have captured a genuine email address from someone who is capable and interested in interacting and then provide an on-screen response. 

The on-screen response is a redirection to a specific thank-you page explaining they need to check their email and click on the link.

All you need to do in the example is swop Amazon.com for your landing page.

By using the variable: redirectURL I can vary the response and use the API and Lambda for a range of different forms on different website pages. I can set the redirect as a hidden form field in the form itself if I want to.

<div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
<div class="snippet-code">
<pre class="snippet-code-js lang-js prettyprint-override"><code> let redirectURL= 'https://amazon.com/';
 var response = {
 "statusCode": 302,
 "headers": {
 Location: redirectURL,
 }
 };
 callback(null, response);</code></pre>
</div>
</div>

blocks|key|4408570|text|要使用lambda函数和api网关将一些结果重定向到其他uri，您必须使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4408571|在lambda函数中的var+err+=+new+Error("HandlerDemo.ResponseFound+Redirection:+Resource+found+elsewhere");+err.name+=+result;+context.done(err,+{});，因此它将在上下文中转发错误，并且在api网关上，方法Response:>添加HTTP作为302响应头的302添加位置|offset|length|style|CODE|4408572|For+Mapping+Integration+Response+Header+Mapping+Location++++integration.response.body.errorType|4408573|这将会起作用|4408574|来自此url+https://aws.amazon.com/blogs/compute/redirection-in-a-serverless-api-with-aws-lambda-and-amazon-api-gateway/的配额|4408575|entityMap|0|LINK|mutability|MUTABLE|url|https://aws.amazon.com/blogs/compute/redirection-in-a-serverless-api-with-aws-lambda-and-amazon-api-gateway/^0|0|B|3L|0|0|W|X|1Q|0|0|7|30|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|15|8|@]|9|@$D|16|E|17|1|18]]|A|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

To redirect some result to other uri using lambda function and api gateway , you have to use 

<code>var err = new Error("HandlerDemo.ResponseFound Redirection: Resource found elsewhere");
err.name = result;
context.done(err, {});
</code>
in lambda function so context it will forward the error
And on api gateway 
`Method Response:> 
Add HTTP STATUS as 302
Response Headers for 302
Add Location

<code>
For Mapping
Integration Response
</code>
<code>Header Mapping
Location integration.response.body.errorType
</code>

This will work

credits from this url <a href="https://aws.amazon.com/blogs/compute/redirection-in-a-serverless-api-with-aws-lambda-and-amazon-api-gateway/" rel="nofollow noreferrer">https://aws.amazon.com/blogs/compute/redirection-in-a-serverless-api-with-aws-lambda-and-amazon-api-gateway/</a>

I am trying to make the redirect work in AWS API gateway. I configured the method response to include Location in the header and on the Integration Response, I set the parameter as : Location = integration.response.body.location. however, when I test the API, instead of redirecting me to the location, it just shows me the text for the location on the API page. Has anyone encountered this before?

The string shown is actually the correct location but the API does not redirect me to that URL.

redirecting from aws api gateway using response 302

我正在尝试使重定向在AWS API网关中工作。我将方法响应配置为在报头中包含Location，并在集成响应上将参数设置为: Location = integration.response.body.location。但是，当我测试API时，它不会将我重定向到该位置，而只是在API页面上显示该位置的文本。以前有没有人遇到...

问使用响应302从aws api网关重定向
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用响应302从aws api网关重定向EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用响应302从aws api网关重定向
EN