Notice
Recent Posts
Recent Comments
Link
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | |||||
3 | 4 | 5 | 6 | 7 | 8 | 9 |
10 | 11 | 12 | 13 | 14 | 15 | 16 |
17 | 18 | 19 | 20 | 21 | 22 | 23 |
24 | 25 | 26 | 27 | 28 | 29 | 30 |
Tags
- 비전공이지만 개발자로 먹고삽니다
- 스코프
- 모던 자바스크립트 Deep Dive
- 프론트엔드 성능 최적화 가이드
- 블로그 서비스 최적화
- 딥다이브
- 프로그래머스
- 디스트럭처링
- const
- 자바스크립트
- 제너레이터와 async/await
- Set과 Map
- 인터넷 장비
- 자바스크립트 딥다이브
- package management
- 빌트인 객체
- 커리어
- 올림픽 통계 서비스 최적화
- 이벤트
- Babel과 Webpack
- Property Attribute
- var 사용금지
- DOM
- 프로퍼티 어트리뷰트
- peerdependencies
- 전역변수의문제점
- ES6함수 추가기능
- 브라우저의 렌더링 과정
- 이미지 갤러리 최적화
- 자바스크립트 패턴
Archives
- Today
- Total
Dev Blog
Difference between URI and URL 본문
The terms “URI” and “URL” are often used interchangeably, but they are not exactly the same.
- A URI is an identifier of a specific resource. Like a page, or book, or a document.
- A URL is special type of identifier that also tells you how to access it, such as HTTPs, FTP, etc.—like https://www.google.com.
- If the protocol (https, ftp, etc.) is either present or implied for a domain, you should call it a URL—even though it’s also a URI.
All butterflies fly, but not everything that flies is a butterfly.
- A Uniform Resource Identifier (URI) provides a simple and extensible means for identifying a resource (straight from *RFC 3986). It’s just an identifier; don’t overthink it.
- For most debates about this that matter, URI is the superset, so the question is just whether a given URI is formally a URL or not. All URLs are URIs, but not all URIs are URLs. In general, if you see http(s)://, it’s a URL.
- URIs technically do require a scheme (see above), but the RFC also says they can be a name, locator, or both, so YOLO! My advice for anyone saying URIs do or do not require a scheme is to show them this article, because it’s the only thing I know of that highlights the contradictions in the RFC.
- Fragments like file.htm actually are not URNs, because URNs are required to use a special notation with urn: in the beginning.
- A little-known section of RFC 3986 actually speaks directly to the religious part of the argument, and seems to say we should say URI instead of URL.
Summary
What a mess. Here’s the TL;DR…
- The RFCs are ancient, poorly written, and not worth debating until they’re updated.
- A URI is an identifier.
- A URL is an identifier that tells you how to get to it.
- Use the term that is best understood by the recipient.
*RFC
: RFC(Request for Comments) 문서는 비평을 기다리는 문서라는 의미로, 컴퓨터 네트워크 공학 등에서 인터넷 기술에 적용 가능한 새로운 연구, 혁신, 기법 등을 아우르는 메모를 나타낸다.
URL
For more Information:
'Web Development > General Tech Knowledges' 카테고리의 다른 글
How to Set up S3 bucket (0) | 2021.04.11 |
---|---|
프론트엔드 필수 반응형 CSS 단위 정리 (0) | 2021.04.08 |
Rest API (0) | 2021.04.06 |
정적 웹 페이지, 동적 웹 페이지의 차이 (0) | 2020.04.17 |
WEB 과 WAS 의 차이점 (0) | 2020.04.17 |
Comments