kylefang/DefinitelyTyped
1
0
Fork 0
mirror of https://github.com/zhigang1992/DefinitelyTyped.git synced 2026-04-21 21:31:12 +08:00
Code Issues Packages Projects Releases Wiki Activity

yar: fix incorrect option location

Browse Source
This commit is contained in:
Simon Schick
2018-03-02 04:25:55 +01:00
parent d8eae6101a
commit e115c06ec8
1 changed files with 20 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
types/yar/index.d.ts vendored
View File

@@ -13,27 +13,6 @@ import {
} from 'hapi';
declare namespace yar {
interface YarOptions {
/**
* Tells Hapi that it should not respond with a HTTP 400 error if the session cookie cannot decrypt.
* This could happen if the cookie is changed on the client, or more likely, if you change the cookie password in your settings.
* If you want to make this condition send an error like it did in prior versions, change this to `false`,
* but be aware that if you change your cookie password you will cause 400 errors to be returned to end users.
* In that case you should probably change this back to true for a short time to allow session cookies to get reset for the best user experience.
* Defaults to true.
*/
ignoreErrors?: boolean;
/**
* Tells Hapi that if a session cookie is invalid for any reason,
* to clear it from the browser.
* This prevents Hapi from having to reprocess the bad cookie on future requests.
* In general you'll probably want this on,
* but if you'd prefer that session cookies be dealt with in some
* other way you may set this to false.
* Defaults to true
*/
clearInvalid?: boolean;
/**
* Determines the name of the cookie used to store session information.
* Defaults to session.
@@ -72,6 +51,26 @@ declare namespace yar {
* the configuration for cookie-specific features:
*/
cookieOptions: {
/**
* Tells Hapi that it should not respond with a HTTP 400 error if the session cookie cannot decrypt.
* This could happen if the cookie is changed on the client, or more likely, if you change the cookie password in your settings.
* If you want to make this condition send an error like it did in prior versions, change this to `false`,
* but be aware that if you change your cookie password you will cause 400 errors to be returned to end users.
* In that case you should probably change this back to true for a short time to allow session cookies to get reset for the best user experience.
* Defaults to true.
*/
ignoreErrors?: boolean;
/**
* Tells Hapi that if a session cookie is invalid for any reason,
* to clear it from the browser.
* This prevents Hapi from having to reprocess the bad cookie on future requests.
* In general you'll probably want this on,
* but if you'd prefer that session cookies be dealt with in some
* other way you may set this to false.
* Defaults to true
*/
clearInvalid?: boolean;
/**
* (Required) used to encrypt and sign the cookie data.
* Must be at least 32 chars.