URL inputs help browsers recognize and check web-address-looking values. They are useful when a user is asked to submit a link to a website. We will keep the example small, so you can see how the fields work without building a whole application first.
What You Need to Know
A valid-looking URL can still lead to an unsafe or unavailable resource. Applications must check destinations and allowed schemes according to their purpose.
A form is like a question sheet. The label asks the question, the control holds the answer, and the name tells the receiving application what that answer is called.
Example: See It in Action
Take a look at this small piece of HTML. You can use it in a practice document and change the text to make it your own.
This is a short HTML fragment. To try it as a webpage, put it inside the body element of a complete HTML document.
<form action="/submit-link" method="post">
<label for="website">Your website</label>
<input type="url" id="website" name="website" placeholder="https://example.test" required>
<button type="submit">Send link</button>
</form>Let’s Understand the Example
- Input creates a form control. Its type decides whether people type text, choose a date, move a slider and more.
- Label tells people what a control is for. For connects the label to the control with the matching id.
- Type changes the kind of input, script, resource or button, depending on the element.
- Action names the destination where the browser sends a form submission. A real server handler must exist there.
- Method controls how a form submits; GET makes values part of the URL, while POST sends them in the request body.
- For links a label to the input whose id matches, so clicking the label can focus the control.
The browser can submit values with keys such as website. A control without a name normally contributes no entry. Whether the submission produces a result depends on the action URL and the server behind it.
What Should You See?
You should see controls for Your website. The example uses an input of type url and sends a POST request when submitted. If the action points to a missing server endpoint, the browser cannot complete the task.
Choose one field and predict its submitted name and value. Then change the value and check whether the browser accepts it. Do not assume that a working-looking form has a real server behind it.
Try It Yourself
- Try a value without a scheme and compare it with a complete https address.
- Save your changes, open or refresh the page, and compare the result with the original example.
- Tell a friend what your change did. If you are not sure, undo it, refresh the page, and compare.
Common Beginner Mistakes
- Treating a URL that passes the browser check as automatically trustworthy.
- Client-side HTML validation is a helpful first check, not a security boundary. A real receiving application must validate the values again.
Key Takeaways
- URL inputs help browsers recognize and check web-address-looking values.
- Input creates a form control. Its type decides whether people type text, choose a date, move a slider and more.
- A valid-looking URL can still lead to an unsafe or unavailable resource. Applications must check destinations and allowed schemes according to their purpose.