-
Notifications
You must be signed in to change notification settings - Fork 26
Uniform Resource Locator (URL)
In order to get anywhere on the web, we need to know the location of of the document, or resource, we want to retrieve. This is specified by a URL:
hostname
┌───┴────┐
https://reddit.com/r/gifs
└─┬─┘ └──┬──┘
scheme path
A URL can be broken down into the following parts:
-
scheme - The scheme helps us to determine the protocol which we will
use to make a request. In this case,
HTTP Secure. Some other schemes we
could use here are
ftp
,mailto
, ornews
. - hostname - The name which is used to identify the Host, or server of the information we wish to retrieve. Behind the scenes, this hostname must be translated to an IP address. DNS servers handle this process.
- path - This indicates to the server the resource we wish to retrieve.
hostname fragment
┌───────┴──────┐ ┌───┴───┐
https://en.wikipedia.org/wiki/Fragment_identifier#Examples
└─┬─┘ └───────────┬───────────┘
scheme path
Fragments allow us to jump to an id
within a document. This is useful when
the information you want someone to view is a few pages down within a HTML
document. Try visiting the above URL in your browser.
More on fragments, here
Consider this example URL generated when performing a search via Google.
hostname query string
┌───┴────┐ ┌──────┴───────┐
https://google.com/search?q=cats&tbm=isch
└─┬─┘ └──┬──┘
scheme path
The query string, aka params, is a series of key/value pairs, which
allows the client to pass some information to the server. In many cases, this
information is usually provided by the user by submitting a form. In this
specific case, the query string indicates that we have performed an image
search for cats
.
key | value |
---|---|
q (query) | cats |
tbm (type of search) | isch (image search) |
More on query string parameters, here
- Team Working Agreement
- Team composition
- Workflows and processes
- Testing and bug filing
- Accessing eAPD
- Active Documentation:
- Sandbox Environment
- Glossary of acronyms
- APDs 101
- Design iterations archive
- MMIS Budget calculations
- HITECH Budget calculations
- Beyond the APD: From Paper to Pixels
- UX principles
- User research process
- Visual styling
- Content guide
- User research findings
- eAPD pilot findings
- User needs
- Developer info
- Development environment
- Coding Standards
- Development deployment
- Infrastructure Architecture
- Code Architecture
- Tech 101
- Authentication
- APD Auto Saving Process
- Resetting an Environment
- Hardware Software List
- Deploying Staging Production Instances Using Scripts
- Terraform 101 for eAPD
- Provisioning Infrastructure with Terraform
- WebSocket basics
- Operations-and-Support-Index
- Single Branch Deployment Strategy
- Ops and Support Overview
- Service Level AOI
- Incident Response Plan
- On-Call Policy
- Infrastructure Contingency Plan
- Updating CloudFront Security Headers
- Requesting and Installing TLS Certificates