Advertisement
Guest User

Untitled

a guest
Jun 1st, 2016
66
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.75 KB | None | 0 0
  1. <html>
  2. <head>
  3. <meta charset="UTF-8" />
  4. <title>Report</title>
  5. <link rel="stylesheet" type="text/css" href="TheaterStyle.css" />
  6. </head>
  7.  
  8. <body>
  9. <img src="../ITF_Assets/Logo.jpg">
  10. <h1>Report</h1>
  11. <div id = "navbar">
  12. <ul>
  13. <li><a href="Homepage.php">Homepage</a></li>
  14. <li><a href="MovieList.php">MovieList</a></li>
  15. <li><a href="SessionList.php">SessionList</a></li>
  16. <li><a href="Report.php">Report</a></li>
  17. <li><a href="SignUp.php">SignUp</a></li>
  18. </ul>
  19. </div>
  20. <h1>Question:</h1>
  21. <h2>1. What is HTML?</h2>
  22. //HyperText Markup Language(HTML)<br>
  23. //HTML is a computer language devised to allow website creation.<br>
  24. //These websites can then be viewed by anyone else connected to the Internet.<br>
  25. //It is relatively easy to learn, with the basics being accessible to most people in one sitting;<br>
  26. //and quite powerful in what it allows you to create.<br>
  27.  
  28. <h2>2. What is CSS?</h2>
  29. //Cascading Style Sheets(CSS)<br>
  30. //CSS describes how HTML elements are to be displayed on screen, paper, or in other media<br>
  31. //CSS saves a lot of work. It can control the layout of multiple web pages all at once<br>
  32. //External stylesheets are stored in CSS files<br>
  33.  
  34. <h2>3. In HTML what does “Hotlink an image” mean, what is hotlinking? Is hotlinking bad?</h2>
  35. is the use of a linked object, often an image, on one site by a web page belonging to a second site.<br>
  36. One site is said to have an inline link to the other site where the object is located.<br>
  37. It is bad because if we just copy the link from other website, when that website change the link, our link will be useless.<br>
  38.  
  39. <h2>4. What is PHP and what does PHP do?</h2>
  40. //PHP (recursive acronym for PHP: Hypertext Preprocessor)<br>
  41. //It is a widely-used open source general-purpose scripting language that is especially suited for web development<br>
  42. //and can be embedded into HTML.<br>
  43. PHP is mainly focused on server-side scripting,<br>
  44. //so you can do anything any other CGI program can do, such as collect form data, generate dynamic page content, or send and receive cookies.<br>
  45. //But PHP can do much more.<br>
  46. //There are three main areas where PHP scripts are used.<br>
  47. //Server-side scripting.<br>
  48. //Command line scripting.<br>
  49. //Writing desktop applications.<br>
  50.  
  51. <h2>5. How does PHP and HTML relate to each other?</h2>
  52. //PHP and HTML interact a lot:<br>
  53. //PHP can generate HTML, and HTML can pass information to PHP.<br>
  54. //Before reading these faqs, it's important you learn how to retrieve variables from external sources.<br>
  55. //The manual page on this topic includes many examples as well.<br>
  56.  
  57. <h2>6. Explain the difference between POST and GET requests. When should post be used? When should GET be used?</h2>
  58. //GET - Requests data from a specified resource<br>
  59. //POST - Submits data to be processed to a specified resource<br>
  60. //
  61. GET requests can be cached<br>
  62. GET requests remain in the browser history<br>
  63. GET requests can be bookmarked<br>
  64. GET requests should never be used when dealing with sensitive data<br>
  65. GET requests have length restrictions<br>
  66. GET requests should be used only to retrieve data<br>
  67. //
  68. POST requests are never cached<br>
  69. POST requests do not remain in the browser history<br>
  70. POST requests cannot be bookmarked<br>
  71. POST requests have no restrictions on data length<br>
  72.  
  73. <h2>7. What is trusted data & untrusted data? Please provide some examples of each.</h2>
  74.  
  75. <h2>8. What is SQL Injection? How does it work? Can you give an example?</h2>
  76. //SQL injection (SQLi) refers to an injection attack wherein an attacker can execute malicious SQL<br>
  77. //statements that control a web application's database server<br>
  78. //SQL Injections can manipulate data (delete, update, add ecc...) and corrupt or delete tables of the database.<br>
  79. <br>
  80.  
  81. <h2>9. Is our website safe from SQL Injection?</h2>
  82. //NO<br>
  83. //SQL Injection Attack<br>
  84. //SQL stands for Structured Query Language. It comes in many different dialects, most of which are based on the SQL-92 ANSI standard.<br>
  85. //An SQL query comprises one or more SQL commands<br>
  86. //It’s these types of queries that make the SQL language so popular and flexible… it’s also what makes it open to SQL injection attacks.<br>
  87.  
  88. <h2>10. What is Cross Site Scripting (XSS) & how does it work?</h2>
  89. Cross-site Scripting (XSS) refers to client-side code injection attack wherein an attacker can execute malicious scripts (also commonly referred to as a malicious payload) into a legitimate website or web application.<br>
  90. //XSS is amongst the most rampant of web application vulnerabilities and occurs when a web application makes use of unvalidated or unencoded user input within the output it generates.<br>
  91. //In order to run malicious JavaScript code in a victim’s browser, an attacker must first find a way to inject a payload into a web page that the victim visits.<br>
  92. //Of course, an attacker could use social engineering techniques to convince a user to visit a vulnerable page with an injected JavaScript payload.<br>
  93. //In order for an XSS attack to take place the vulnerable website needs to directly include user input in its pages.<br>
  94. //An attacker can then insert a string that will be used within the web page and treated as code by the victim’s browser.<br>
  95. <h2>11. Is our website safe from XSS?</h2>
  96.  
  97. <h2>12. What are web cookies?</h2>
  98. //An HTTP cookie (also called web cookie, Internet cookie, browser cookie or simply cookie) is a small piece of data sent from a website and stored in the user's web browser while the user is browsing.<br>
  99. <h2>13. Are cookies bad?</h2>
  100. //NO.<br>
  101. //Some sites may be collecting demographic information about who are visiting their site,<br>
  102. //how often they visit the site, how long they stay on the site, the visitors' surfing habits etc.<br>
  103. //Some sites may use cookies to monitor advertisements.<br>
  104. //It helps them decide what ads they let you see, and how often you see them.<br>
  105. //More importantly, cookies help web servers to personalize the web page for you, and sometimes let you enter a page on a secure server not requiring you to type in your password every time.<br>
  106. //any shopping sites keep a track of what you bought or searched for from their site earlier and keep this information in a cookie.<br>
  107.  
  108. <h2>14. How much disk space does the website require? Including images.</h2>
  109. <br>
  110.  
  111. <h2>15. What are HTTP Status codes?</h2>
  112. // It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes.<br>
  113. //The first digit of the status code specifies one of five classes of response;<br>
  114. //an HTTP client must recognise these five classes at a minimum.<br>
  115. //The phrases used are the standard wordings, but any human-readable alternative can be provided.<br>
  116. <h2>//Unless otherwise stated, the status code is part of the HTTP/1.1 standard</h2>
  117.  
  118. <h2>16. Describe the HTTP status codes listed below:</h2>
  119. o 200://This is the most common HTTP status message.<br>
  120. //It indicates that the request was successful and the server was able to deliver on the request.<br>
  121. o 302://(Found)The requested resource resides temporarily in another location, but it can still be found at the requested URI.<br>
  122. o 400://(Bad Request)The request could not be understood by the server due to malformed syntax.<br>
  123. o 403://(Forbidden)The server understood the request, but refuses to fulfill it. Authorization, in this case, doesn't matter.<br>
  124. o 404://(Not Found)This is the most easily recognized error message. It states that the URI requested does not exist on the server.<br>
  125. o 500://(Internal Server Error)The server encountered something unexpected that didn't allow it to complete the request.<br>
  126. // This is often seen with CGI scripts that have problems.<br>
  127.  
  128. </body>
  129. </html>
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement