Diclib.com
Словарь ChatGPT

Поиск в словаре Индивидуальные решения

Введите слово или словосочетание на любом языке 👆

Язык:

Перевод и анализ слов искусственным интеллектом ChatGPT

На этой странице Вы можете получить подробный анализ слова или словосочетания, произведенный с помощью лучшей на сегодняшний день технологии искусственного интеллекта:

как употребляется слово
частота употребления
используется оно чаще в устной или письменной речи
варианты перевода слова
примеры употребления (несколько фраз с переводом)
этимология

Что (кто) такое HTTP cookies - определение

SMALL PIECE OF DATA SENT FROM A WEBSITE AND STORED ON THE USER'S COMPUTER BY THE USER'S WEB BROWSER

Internet cookie; WWW cookie; WWW browser cookie; Browser cookie; Web browser cookie; Web cookie; HTTP Cookie; HTTP cookies; Http cookie; Cookie grabber; Cookie file; Cookie poisoning; Internet cookies; Cookie (computing); Cookie (computer); Http cookies; Cookie (computers); Tracking cookie; Enable cookies; COOKIES.TXT; HttpOnly; Internet Cookies; Tracking cookies; Web cookies; Web browser cookies; Browser cookies; WWW browser cookies; Third-party cookie; Cookie (web); Session cookie; HTTPOnly; Computer cookie; Cookie (browser); Cookies (Internet); Cookie (internet); Crumb (computing); Cookiejacking; Super cookie; Supercookie; Supercookies; Cookie interception; Cookie sniffing; Cookie theft; Authentication cookie; Cookie notify; Cookie notice; Cookie (software); Cookie tracking; Third party cookie; Webcookies; First-party cookie; First party cookie; 3rd party cookie; 3rd-party cookie; 1st party cookie; 1st-party cookie; HttpOnly cookie; SameSite cookie; Same-site cookie; Http-only cookie; In-memory cookie; Transient cookie; Non-persistent cookie; Persistent cookie; Super-cookie; Third-party cookies; Alternatives to HTTP cookies; EU cookie directive; Privacy concerns with HTTP cookies

Найдено результатов: 200

HTTP cookie

<World-Wide Web> A system invented by Netscape to allow a web server to send a web browser a packet of information that will be sent back by the browser each time it accesses the same server. Cookies can contain any arbitrary information the server chooses to put in them and are used to maintain state between HTTP transactions, which are otherwise stateless. Typically this is used to authenticate or identify a registered user of a website without requiring them to sign in again every time they access it. Other uses are, e.g. maintaining a "shopping basket" of goods you have selected to purchase during a session at a site, site personalisation (presenting different pages to different users) or tracking which pages a user has visited on a site, e.g. for marketing purposes. The browser limits the size of each cookie and the number each server can store. This prevents a malicious site consuming lots of disk space. The only information that cookies can return to the server is what that same server previously sent out. The main privacy concern is that, by default, you do not know when a site has sent or received a cookie so you are not necessarily aware that it has identified you as a returning user, though most reputable sites make this obvious by displaying your user name on the page. After using a shared login, e.g. in an Internet cafe, you should remove all cookies to prevent the browser identifying the next user as you if they happen to visit the same sites. http://cookiecentral.com/c_concept.htm">Cookie Central (http://cookiecentral.com/c_concept.htm). (2004-08-26)

HTTP cookie

HTTP cookies (also called web cookies, Internet cookies, browser cookies, or simply cookies) are small blocks of data created by a web server while a user is browsing a website and placed on the user's computer or other device by the user's web browser. Cookies are placed on the device used to access a website, and more than one cookie may be placed on a user's device during a session.

https://en.wikipedia.org/wiki/HTTP_cookie

computer cookie

HTTP cookie

cookie file

<operating system> A collection of fortune cookies in a format that facilitates retrieval by a fortune program. There are many cookie files in public distribution, and site admins often assemble their own from various sources. [Jargon File] (1997-01-07)

HTTP message body

HTTP body data; HTTP response message body; Http message body

HTTP Message Body is the data bytes transmitted in an HTTP transaction message immediately following the headers if there are any (in the case of HTTP/0.9 no headers are transmitted).

https://en.wikipedia.org/wiki/HTTP_message_body

HTTP header injection

WEB APPLICATION VULNERABILITY THAT OCCURS WHEN HTTP HEADERS ARE DYNAMICALLY GENERATED FROM USER INPUT; CAN ALLOW FOR HTTP RESPONSE SPLITTING, SESSION FIXATION (VIA SET-COOKIE), CROSS-SITE SCRIPTING, AND MALICIOUS REDIRECT ATTACKS

HTTP Header Injection

HTTP header injection is a general class of web application security vulnerability which occurs when Hypertext Transfer Protocol (HTTP) headers are dynamically generated based on user input. Header injection in HTTP responses can allow for HTTP response splitting, Session fixation via the Set-Cookie header, cross-site scripting (XSS), and malicious redirect attacks via the location header.

https://en.wikipedia.org/wiki/HTTP_header_injection

HTTP/3

THIRD MAJOR VERSION OF THE HTTP NETWORK PROTOCOL

Http3; HTTP 3; HTTP3

(HTTP/3 also uses the completed QUIC protocol described in RFC 9000 and related RFCs such as RFC 9001)

https://en.wikipedia.org/wiki/HTTP/3

HTTP/1.0

APPLICATION PROTOCOL FOR DISTRIBUTED, COLLABORATIVE, HYPERMEDIA INFORMATION SYSTEMS

Http; Http protocol; Hyper Text Transfer Protocol; HTTP request; Http://; Hypertext Transfer Protocol; HyperText Transfer Protocol; Http request; HTTP/1.1; Htttp; Http;; Http.; Request method; HTTP://; HTTP HEAD; HTTP GET; HTTP PUT; HTTP TRACE; HTTP OPTIONS; HTTP CONNECT; GET request; HEAD request; PUT request; DELETE request; TRACE request; OPTIONS request; CONNECT request; HTTP HEAD request; HTTP GET request; HTTP PUT request; HTTP DELETE request; HTTP TRACE request; HTTP OPTIONS request; HTTP CONNECT request; Hypertext transfer protocall; HTTP DELETE; HTTP Verbs; Hypertext Protocol; HTTP Requests; Http post/get requests; Http upload; HTTP/0.9; HTTP/1.0; HTTP 0.9; HTTP 1.0; HTTP 1.1; GET (HTTP); Http session; HTTP method; HTTP Protocol; HTTP protocol; Http:\\; PUT (HTTP); DELETE (HTTP); HEAD (HTTP); OPTIONS (HTTP); TRACE (HTTP); CONNECT (HTTP); HTTP response; Hypertext Transport Protocol; HTTP-NG; GET requests; HTTPA; RFC 2616; RFC2616; HTTP verbs; Http:; Hypertext transfer protocol; HTTP requests; Hyper-text transfer protocol

Hypertext Transfer Protocol version 1.0.

Hypertext Transfer Protocol

APPLICATION PROTOCOL FOR DISTRIBUTED, COLLABORATIVE, HYPERMEDIA INFORMATION SYSTEMS

Http; Http protocol; Hyper Text Transfer Protocol; HTTP request; Http://; Hypertext Transfer Protocol; HyperText Transfer Protocol; Http request; HTTP/1.1; Htttp; Http;; Http.; Request method; HTTP://; HTTP HEAD; HTTP GET; HTTP PUT; HTTP TRACE; HTTP OPTIONS; HTTP CONNECT; GET request; HEAD request; PUT request; DELETE request; TRACE request; OPTIONS request; CONNECT request; HTTP HEAD request; HTTP GET request; HTTP PUT request; HTTP DELETE request; HTTP TRACE request; HTTP OPTIONS request; HTTP CONNECT request; Hypertext transfer protocall; HTTP DELETE; HTTP Verbs; Hypertext Protocol; HTTP Requests; Http post/get requests; Http upload; HTTP/0.9; HTTP/1.0; HTTP 0.9; HTTP 1.0; HTTP 1.1; GET (HTTP); Http session; HTTP method; HTTP Protocol; HTTP protocol; Http:\\; PUT (HTTP); DELETE (HTTP); HEAD (HTTP); OPTIONS (HTTP); TRACE (HTTP); CONNECT (HTTP); HTTP response; Hypertext Transport Protocol; HTTP-NG; GET requests; HTTPA; RFC 2616; RFC2616; HTTP verbs; Http:; Hypertext transfer protocol; HTTP requests; Hyper-text transfer protocol

<protocol> (HTTP) The client-server TCP/IP protocol used on the World-Wide Web for the exchange of HTML documents. It conventionally uses port 80. Latest version: HTTP 1.1, defined in RFC 2068, as of May 1997. See also Uniform Resource Locator. (1994-10-27)

HTTP persistent connection

USING A SINGLE TCP CONNECTION TO SEND AND RECEIVE MULTIPLE HTTP REQUESTS/RESPONSES

Keep-alive connections; Persistent connections; Persistent connection; Keep-alive connection; HTTP persistent connections; Persistent HTTP; HTTP keep-alive

HTTP persistent connection, also called HTTP keep-alive, or HTTP connection reuse, is the idea of using a single TCP connection to send and receive multiple HTTP requests/responses, as opposed to opening a new connection for every single request/response pair. The newer HTTP/2 protocol uses the same idea and takes it further to allow multiple concurrent requests/responses to be multiplexed over a single connection.

https://en.wikipedia.org/wiki/HTTP_persistent_connection

Википедия

HTTP cookie

HTTP cookies (also called web cookies, Internet cookies, browser cookies, or simply cookies) are small blocks of data created by a web server while a user is browsing a website and placed on the user's computer or other device by the user's web browser. Cookies are placed on the device used to access a website, and more than one cookie may be placed on a user's device during a session.

Cookies serve useful and sometimes essential functions on the web. They enable web servers to store stateful information (such as items added in the shopping cart in an online store) on the user's device or to track the user's browsing activity (including clicking particular buttons, logging in, or recording which pages were visited in the past). They can also be used to save for subsequent use information that the user previously entered into form fields, such as names, addresses, passwords, and payment card numbers.

Authentication cookies are commonly used by web servers to authenticate that a user is logged in, and with which account they are logged in. Without the cookie, users would need to authenticate themselves by logging in on each page containing sensitive information that they wish to access. The security of an authentication cookie generally depends on the security of the issuing website and the user's web browser, and on whether the cookie data is encrypted. Security vulnerabilities may allow a cookie's data to be read by an attacker, used to gain access to user data, or used to gain access (with the user's credentials) to the website to which the cookie belongs (see cross-site scripting and cross-site request forgery for examples).

Tracking cookies, and especially third-party tracking cookies, are commonly used as ways to compile long-term records of individuals' browsing histories — a potential privacy concern that prompted European and U.S. lawmakers to take action in 2011. European law requires that all websites targeting European Union member states gain "informed consent" from users before storing non-essential cookies on their device.

https://en.wikipedia.org/wiki/HTTP cookie