Server-side code and client-side code serve different purposes and operate in distinct environments within a web application. They are executed independently and have separate scopes.
Client-Side Code
This code is executed in the user's web browser. It includes languages like HTML, CSS, and JavaScript. Client-side code controls how the content is displayed and interacts with users. Client-side code cannot directly access server-side resources or data. Osano cookie consent operates client-side.
Server-Side Code
This code runs on the web server. It often involves languages like Python, PHP, Ruby, Java, or Node.js. Server-side code handles data processing, database queries, business logic, and generating dynamic content to be sent to the client. This code executes BEFORE client-side code and is often loaded in the site headers.
What does this mean for Osano?
The Osano cookie consent may not be able to discover or affect server-side cookies by default and may require a URL scan or manual entry to accomplish identification for disclosure purposes.
In certain cases, you may be able to utilize the Cookie Consent API to read a user's consent preferences and then affect server-side cookies.