# Set up response template for redirect
**URL:** https://forum.serverless.com/t/set-up-response-template-for-redirect/340
**Category:** Serverless Framework
**Created:** [September 20, 2016, 9:04am UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340 "2016-09-20T09:04:09Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@yuhwan](https://forum.serverless.com/u/yuhwan)
#### Post date: [September 20, 2016, 9:04am UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/1 "2016-09-20T09:04:09Z")
When I use serverless v0.5, I was able to easily set up a 302 status code in the s-function.json file like below.
```
"default": {
"statusCode": "302",
"responseParameters": {
"method.response.header.Location": "integration.response.body.location"
}...
```
But, I couldn’t find the way to specify the 302 status code and responseParameter in a serverless.yml (Serverless v1.0-rc). Is there a way of doing this?
---
### Author:  [@buggy](https://forum.serverless.com/u/buggy)
#### Post date: [October 10, 2016, 4:30am UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/2 "2016-10-10T04:30:27Z")
I was looking for this too. It looks like the 1.0 RC’s are hard coded for a limited number of [response codes](https://github.com/serverless/serverless/blob/242ad7bab4d44bf4c23c4476662e640452f2c5b9/lib/plugins/aws/deploy/compile/events/apiGateway/lib/methods.js#L318-L341). There is a plugin that might help with this [https://github.com/silvermine/serverless-plugin-multiple-responses](https://github.com/silvermine/serverless-plugin-multiple-responses)
---
### Author:  [@yuhwan](https://forum.serverless.com/u/yuhwan)
#### Post date: [October 10, 2016, 6:12am UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/3 "2016-10-10T06:12:49Z")
Thank you for sharing the plugin!
This plugin will suffice to set up the custom responses. 🙂
---
### Author:  [@flomotlik](https://forum.serverless.com/u/flomotlik)
#### Post date: [October 12, 2016, 2:50pm UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/4 "2016-10-12T14:50:27Z")
With the latest master and the proxy integration you can simply return the `status code` from code now. This should make this a lot simpler.
---
### Author:  [@Hainesy](https://forum.serverless.com/u/Hainesy)
#### Post date: [October 14, 2016, 12:55pm UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/5 "2016-10-14T12:55:17Z")
Hi @flomotlik, can you elaborate on this? How would one return a 302 status code along with URL to redirect to?
---
### Author:  [@flomotlik](https://forum.serverless.com/u/flomotlik)
#### Post date: [October 14, 2016, 2:16pm UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/6 "2016-10-14T14:16:12Z")
The proxy integration allows you to set headers and status code directly so you simply set the 302 status code and the applicable header (e.g. Location:) and you should be all set:
apigateway proxy: [http://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-set-up-simple-proxy.html](http://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-set-up-simple-proxy.html)
Our docs are currently a bit wrong as you shouldn’t use the context.succeed method, but simply use the callback that is also provided. But you get the picture from here:
Our documentation: [https://serverless.com/framework/docs/providers/aws/events/apigateway/](https://serverless.com/framework/docs/providers/aws/events/apigateway/)
---
### Author:  [@Hainesy](https://forum.serverless.com/u/Hainesy)
#### Post date: [October 17, 2016, 12:34pm UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/8 "2016-10-17T12:34:19Z")
Hi @flomotlik, I still can’t get this to work.
Here’s my lambda function:
```
module.exports.testRedirect = (event, context, callback) => {
const response = {
statusCode: 302,
headers: {
"Location": "https://www.google.co.uk"
}
};
callback(null, response);
};
```
And here’s my yaml configuration:
```
functions:
testRedirect:
handler: handler.testRedirect
events:
- http:
path: test
method: get
integration: lambda-proxy
```
I’ve tried both “lambda” and “lamda-proxy” integrations, but all I get back is the full response JSON in the browser. Am I missing something in my configuration?
* * *
Update: @flomotlik Thank you - that works now with the “body” specified. It’s a shame serverless-offline doesn’t support it.
---
### Author:  [@flomotlik](https://forum.serverless.com/u/flomotlik)
#### Post date: [October 17, 2016, 1:39pm UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/9 "2016-10-17T13:39:05Z")
The response object doesn’t have a body config. Maybe that is the issue. And also check that you have Serverless 1.0.2 installed.
```auto
module.exports.testRedirect = (event, context, callback) => {
const response = {
statusCode: 302,
headers: {
"Location": "https://www.google.co.uk"
},
body: ""
};
callback(null, response);
};
```
---
### Author:  [@chris](https://forum.serverless.com/u/chris)
#### Post date: [November 10, 2016, 6:47am UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/10 "2016-11-10T06:47:05Z")
@flomotlik do you have an example of the equivalent of this when using Java? I tried returning a string of JSON with the similar fields, but that didn’t work (it just passes the JSON straight through to the response/browser). I don’t see a mapping in the AWS API Gateway config that seems like it’d handle a 302, so I’m wondering if this is feasible with Java? If there are any docs for Java examples of this stuff, please point me to that as I may just not be aware of those.
I should note, I have also tried throwing an exception, and combining that with a response mapping. However, I can’t seem to use a dynamic Location header value, as when I deploy I’m told “Invalid mapping expression”. Here’s what I have for the yaml config:
```
functions:
oauthcallback:
handler: LambdaHandler::oauth_callback
events:
- http:
path: oauth/callback
method: get
integration: lambda
request:
template:
application/json: '{ "code" : "$input.params(''code'')" }'
response:
statusCodes:
302:
pattern: ''
headers:
Location: $input.path("$.errorMessage")
```
Note, I tried a template in the response, and that properly uses that same dynamic value, so it may just be that Serverless doesn’t allow a dynamic header value?
I’d still be interested in knowing if there is a better way to do this, or way to use the default mappings and not raise an exception to achieve this, etc.
---
### Author:  [@buggy](https://forum.serverless.com/u/buggy)
#### Post date: [November 10, 2016, 10:53am UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/12 "2016-11-10T10:53:54Z")
@chris You seem to be mixing lambda and lambda proxy integration type. Returning a JSON response with statusCode, headers and body will only work if you’re using lambda-proxy in which case you don’t need the request and response sections in your serverless.yml (you also don’t need the integration: lambda either as it defaults to lambda-proxy).
Assuming your serverless.yml now looks like:
```auto
functions:
oauthcallback:
handler: LambdaHandler::oauth_callback
events:
- http:
path: oauth/callback
method: get
```
Now you just need to write your Lambda function so that it returns a Java bean with statusCode, headers and body properties. Based on the Java examples in the AWS docs I would expect the response class to look something like:
```java
class ResponseClass {
private string statusCode;
public string getStatusCode() {
return this.statusCode;
}
public void setStatusCode(string statusCode) {
this.statusCode = statusCode;
}
...
}
```
---
### Author:  [@chris](https://forum.serverless.com/u/chris)
#### Post date: [November 10, 2016, 5:09pm UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/13 "2016-11-10T17:09:25Z")
@buggy thanks. So, that allows me to do a proper response, but I can’t seem to get the query parameter without doing a mapping (or I’m just not understanding). JSON data from a POST tends to work, but I haven’t seen how to get a query parameter with a GET to work. I am using the POJO approach for my handler (vs. inheriting from the interface). I have a class that has a “code” property, but it never gets set from the “code” query parameter (which is why I had that request template mapping before). Any guidance there? Are query parameters maybe mapped a different way (when I’ve used the JavaScript implementation, I know I had to get them from `event.pathParameters`.
I happen to be doing all this in Kotlin, so it’s possible there is something not translating right, but I’ve done Lambda handlers in Kotlin this same way before and it worked fine (I’ve just never had to use query params, it was always JSON data sent to a POST, which got mapped into my request object just fine).
---
### Author:  [@bbilger](https://forum.serverless.com/u/bbilger)
#### Post date: [November 10, 2016, 6:02pm UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/14 "2016-11-10T18:02:02Z")
@chris
Query parameters in proxy integration can be obtained via event.queryStringParameters which is a map of strings.
I am using the following mapping in my framework: [https://github.com/bbilger/jrestless/blob/master/aws/gateway/jrestless-aws-gateway-core/src/main/java/com/jrestless/aws/gateway/io/GatewayRequest.java](https://github.com/bbilger/jrestless/blob/master/aws/gateway/jrestless-aws-gateway-core/src/main/java/com/jrestless/aws/gateway/io/GatewayRequest.java)
And/Or
[https://github.com/bbilger/jrestless/blob/master/aws/gateway/jrestless-aws-gateway-handler/src/main/java/com/jrestless/aws/gateway/io/GatewayRequestImpl.java](https://github.com/bbilger/jrestless/blob/master/aws/gateway/jrestless-aws-gateway-handler/src/main/java/com/jrestless/aws/gateway/io/GatewayRequestImpl.java)
---
### Author:  [@chris](https://forum.serverless.com/u/chris)
#### Post date: [November 10, 2016, 7:59pm UTC](https://forum.serverless.com/t/set-up-response-template-for-redirect/340/15 "2016-11-10T19:59:06Z")
@bbilger thank you! I have it all working now. The key was adding a `queryStringParameters` field to my request object. Since I only needed that, and only needed a single element from it, I was able to do a nice simple data class:
```
data class Oauth (var queryStringParameters: Map? = null) {
val code : String
get() = queryStringParameters?.get("code") ?: ""
}
```
Thank you everyone for the help!