HTTP stands for Hypertext Transfer Protocol. It describes a request-and-response exchange used on the web. A URL identifies a resource and may include several components, such as a scheme, host, path and query. These concepts work together but do not mean the same thing.
Understand the request and response
A client sends a request and a server returns a response. A page may require several resource requests, including images or scripts. Describe the exchange at the level of the question rather than assuming one browser action involves only one message. The status and headers provide information in addition to the response content.
Read a URL by its components
In “https://example.org/guides?topic=writing#intro”, the scheme is “https”, the host is “example.org”, the path is “/guides”, the query supplies “topic=writing” and the fragment identifies “intro”. A component can be absent. Do not assume every URL includes a query or that each part identifies a separate file on the server.
Distinguish HTTP from HTTPS
HTTPS uses HTTP over a secured transport arrangement. It is not a different type of page content, and a secure connection alone does not prove that everything a website claims is accurate. Keep communication security separate from evaluating the source and purpose of the information presented.
Explain status without guessing the cause
A status code describes the server’s response at the protocol level. A missing resource, refused request or server problem may require investigation beyond the code itself. In coursework, report the actual request and response and explain the relevant meaning. Avoid inventing a detailed cause from a screenshot of one error.
Use technical terms precisely
A domain, a URL, a website and a web page are different concepts. Explain which you mean and use a small example to show the relationship. Check current official documentation for implementation details. A concise description of the protocol and address structure is more useful than a list of acronyms without their roles.
Sources and further reading
Related study guides
- ISO and Evaluation Assurance Levels: Read Technical Claims Carefully
- Database Management Systems: Meaning, Examples and Coursework
- HTML, CSS and Style Sheets: An Assignment Guide
For general study guidance, visit the knowledgebase. Follow your own course requirements when applying this article to assessed work.