Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

75%
+4 −0
Q&A Not obligating http:// or https:// in a url field of a contact form

input type="url" works like this by design: An empty string ("") indicating that the user did not enter a value or that the value was removed. A single properly-formed absolute URL. This doesn'...

posted 3y ago by Alexei‭

Answer
#1: Initial revision by user avatar Alexei‭ · 2021-03-31T05:54:45Z (over 3 years ago)
`input type="url"` works like this [by design](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/url):


 > An empty string ("") indicating that the user did not enter a value or that the value was removed.
> A single properly-formed absolute URL. This doesn't necessarily mean the URL address exists, but it is at least formatted correctly. **In simple terms, this means urlscheme://restofurl.**

While most users do not care about it, there are [lot of URI schemes](https://en.wikipedia.org/wiki/List_of_URI_schemes) out there and the scheme must be provided.

Even in the specific case of http/s, if the web application is correctly configured to automatically redirect `http` to `https` or it does not have a certificate, inferring the scheme might fail.

As a side note, I have such inputs in various applications used by non-tech folks and they are fine with it. This is supported by copy-pasting from the URL address bar in most browser (e.g. Chrome does not show it, but when you copy the URL you also get the scheme).

So, shortly put, **unless there is a very strong reason not to request the scheme, I think you should only accept only valid URLs, that is with http or https.**