From d365077dfa7d9a7353801a529b3fca8552b29959 Mon Sep 17 00:00:00 2001 From: Dawid Winiarczyk Date: Wed, 27 Dec 2017 17:18:13 +0100 Subject: [PATCH] docs(aio): HttpClientXsrfModule withConfig => withOptions (#21185) Docummentation suggests use of HttpClientXsrfModule#withConfig but this method looks like it's renamed to #withConfig. https://angular.io/guide/http#configuring-custom-cookieheader-names PR Close #21185 --- aio/content/guide/http.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aio/content/guide/http.md b/aio/content/guide/http.md index dcce542643..e084e63ccc 100644 --- a/aio/content/guide/http.md +++ b/aio/content/guide/http.md @@ -547,12 +547,12 @@ In order to prevent collisions in environments where multiple Angular apps share ### Configuring custom cookie/header names -If your backend service uses different names for the XSRF token cookie or header, use `HttpClientXsrfModule.withConfig()` to override the defaults. +If your backend service uses different names for the XSRF token cookie or header, use `HttpClientXsrfModule.withOptions()` to override the defaults. ```javascript imports: [ HttpClientModule, - HttpClientXsrfModule.withConfig({ + HttpClientXsrfModule.withOptions({ cookieName: 'My-Xsrf-Cookie', headerName: 'My-Xsrf-Header', }),