Hi,
When I have a non RFC-6265 compliant cookie (like one with a space in the value but not wrapped in quotes) then this /docs route will fail with the message
{"statusCode":400,"error":"Bad Request","message":"Invalid cookie value"}
Hapi provides a way to prevent this, which is setting the route with config like such
server.route({
path: '/',
method: 'GET',
config: {
state: {
parse: false
}
},
So, when this plugin registers its routes, it could first merge the config object with something supplied by the user, both solving this exact scenario and perhaps others.
Hi,
When I have a non RFC-6265 compliant cookie (like one with a space in the value but not wrapped in quotes) then this /docs route will fail with the message
{"statusCode":400,"error":"Bad Request","message":"Invalid cookie value"}Hapi provides a way to prevent this, which is setting the route with config like such
So, when this plugin registers its routes, it could first merge the config object with something supplied by the user, both solving this exact scenario and perhaps others.