![]() Pages render without sensitive private data session and customer DTO objects are emptyįunctionality specific to both current session (customer) and page should be written using JavaScript (e.g., related product listing should exclude items that are already in the shopping cart) Any future HTTP POST or PUT request changes the value of private_content_version and results in the updated content being cached by the browser.Subsequent requests with the same data version are retrieved from local storage. The server’s reply is cached in the browser’s local storage. JavaScript interprets the presence of the private_content_version cookie to mean that private content is present on the page, so it sends an AJAX request to the Magento server to get the current private content.The server generates the private_content_version cookie for this user and returns the response to the browser.The user performs some action, such as adding to a cart, that results in an POST or PUT request to the Magento application. ![]() Private content, which is stored in the browser local storage, uses the private_content_version cookie to store the version. For more information about caching, see RFC-2616 section 13 ![]() Using GET or HEAD methods might trigger caching and prevent updates to private content. Use only HTTP POST or PUT methods to change state (e.g., adding to a shopping cart, adding to a wishlist, etc.) and don’t expect to see caching on these methods. Message Queues (Magento Commerce Edition Only).Upload your component to the Magento Marketplace.Roadmap for developing and packaging components.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |