HTTPCookieManage (Function)

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

This content has been translated automatically. Click here to view the French version.

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

HTTPCookieManage (Function)

In french: HTTPCookieGère

Enables or disables the management of cookies in an HTTP request run:

by HTTPRequest.
Versions 20 and later
or by the HTTPSend or RESTSend function.
New in version 20
or by the HTTPSend or RESTSend function.
or by the HTTPSend or RESTSend function.

Remark: The cookies read and sent by HTTPRequest are only stored in memory in the application. They are not related to the cookies of Web browsers installed on the computer.

Example

// Gère les cookies dans les requêtes sur les sites du domaine "google.fr"
HTTPCookieManage(".google.fr", True)

// Ouverture de la page d'accueil de Google
HTTPRequest("www.google.fr")

// Refait la requête en tenant compte des cookies éventuellement renvoyés au 1er appel
HTTPRequest("www.google.fr/search?hl=fr&source=hp&q=windev")

Syntax

Enabling/Disabling the management of cookies (HTTPRequest) Hide the details

HTTPCookieManage([<Domain>, ] <Activation>)

<Domain>: Character string (with quotes)

Domain onto which the activation or the deactivation is applied.

<Activation>: Boolean

True to enable the management of cookies,
False to disable the management of cookies.
Even if the management of cookies is disabled, you still have the ability to pass cookies in the HTTP request by using the appropriate header in HTTPRequest. Similarly, the cookies returned by the server can be retrieved by HTTPGetResult.

Versions 20 and later

Enabling/Disabling the management of cookies (HTTPSend) Hide the details

HTTPCookieManage(<HTTP request> [, <Domain>] , <Activation>)

<HTTP request>: httpRequest variable

Name of httpRequest variable for which the management of cookies will be enabled or disabled.

<Domain>: Character string (with quotes)

Domain onto which the activation or the deactivation is applied.

<Activation>: Boolean

True to enable the management of cookies,
False to disable the management of cookies.
Even if the management of cookies is disabled, you still have the ability to pass cookies in the HTTP request by using the appropriate header in the httpRequest variable.

New in version 20

Enabling/Disabling the management of cookies (HTTPSend) Hide the details

HTTPCookieManage(<HTTP request> [, <Domain>] , <Activation>)

<HTTP request>: httpRequest variable

Name of httpRequest variable for which the management of cookies will be enabled or disabled.

<Domain>: Character string (with quotes)

Domain onto which the activation or the deactivation is applied.

<Activation>: Boolean

True to enable the management of cookies,
False to disable the management of cookies.
Even if the management of cookies is disabled, you still have the ability to pass cookies in the HTTP request by using the appropriate header in the httpRequest variable.

Enabling/Disabling the management of cookies (HTTPSend) Hide the details

HTTPCookieManage(<HTTP request> [, <Domain>] , <Activation>)

<HTTP request>: httpRequest variable

Name of httpRequest variable for which the management of cookies will be enabled or disabled.

<Domain>: Character string (with quotes)

Domain onto which the activation or the deactivation is applied.

<Activation>: Boolean

True to enable the management of cookies,
False to disable the management of cookies.
Even if the management of cookies is disabled, you still have the ability to pass cookies in the HTTP request by using the appropriate header in the httpRequest variable.

Remarks

The cookies are not kept between two runs of an executable. They must be saved and restored by programming:
- backup: HTTPCookieGet, Serialize and fSaveText
- restoration: functions HTTPCookieReplace, Deserialize and fLoadText.
HTTPGetResult ignores HTTPCookieManage.
When the cookies are enabled:
- the cookies received in response to a call to HTTPRequest are stored while waiting for a future call to HTTPRequest on the same domain. This operating mode is similar to the one of the Internet browsers.
- Versions 20 and later
  the cookies received in response to a call to HTTPSend are stored while waiting for a future call to HTTPSend on the same domain: the httpRequest variable is updated. This operating mode is similar to the one of the Internet browsers.
  New in version 20
  the cookies received in response to a call to HTTPSend are stored while waiting for a future call to HTTPSend on the same domain: the httpRequest variable is updated. This operating mode is similar to the one of the Internet browsers.
  the cookies received in response to a call to HTTPSend are stored while waiting for a future call to HTTPSend on the same domain: the httpRequest variable is updated. This operating mode is similar to the one of the Internet browsers.
- Versions 20 and later
  the cookies received in response to a call to RESTSend are stored while waiting for a future call to RESTSend on the same domain: the restRequest variable is updated. This operating mode is similar to the one of the Internet browsers.
  New in version 20
  the cookies received in response to a call to RESTSend are stored while waiting for a future call to RESTSend on the same domain: the restRequest variable is updated. This operating mode is similar to the one of the Internet browsers.
  the cookies received in response to a call to RESTSend are stored while waiting for a future call to RESTSend on the same domain: the restRequest variable is updated. This operating mode is similar to the one of the Internet browsers.
The use of cookies is required on some sites that use them to supply the identifiers. Then, these identifiers are transmitted to each request (a basket identifier when placing an order for example).
If a management is defined on a domain, this information has priority over the global option.

Component: wd260com.dll