We're looking for a user researcher to understand the needs of developers and designers. Is this you or someone you know? Check out the post: https://mzl.la/2IGzdXS

현재 번역은 완벽하지 않습니다. 한국어로 문서 번역에 동참해주세요.

컴퓨터 네트워크라고 한다면 대개 웹 사이트에 접속하여 정보를 습득하는 인터넷 서핑을 떠올리지만 이 외에도 많은 요소가 존재한다. 예를 들면 이메일을 주고 받는 행위나 특정 파일의 업로드나 다운로드와 같이 데이터의 주고 받음이 일어나는 작업은 모두 컴퓨터 네트워크의 정보 자원(resource)을 이용하는 행위라고 할 수 있다. 인터넷의 발전으로 인해 컴퓨터 네트워크의 범위는 넓어지고 여기에 포함된 정보 자원의 양과 종류도 점차 증가하고 있다.

이렇게 방대한 컴퓨터 네트워크에서 자신이 원하는 정보 자원을 찾기 위해서는 해당 정보 자원의 위치와 종류를 정확히 파악할 필요가 있는데, 이를 나타내는 일련의 규칙을 URL(Uniform Resource Locator: 자원 위치 지정자)이라고 한다. URL에는 컴퓨터 네트워크 상에 퍼져있는 특정 정보 자원의 종류와 위치가 기록되어 있다

The URL interface represents an object providing static methods used for creating object URLs.

When using a user agent where no constructor has been implemented yet, it is possible to access such an object using the Window.URL properties (prefixed with Webkit-based browser as Window.webkitURL).

주의: This feature is available in Web Workers.


URL is used to parse, construct, normalise, and encode URLs.

The constructor takes a url parameter, and an optional base parameter to use as a base if the url parameter is a relative URL:

const url = new URL('../cats', 'http://www.example.com/dogs');
console.log(url.hostname); // "www.example.com"
console.log(url.pathname); // "/cats"

URL properties can be set to construct the URL:

url.hash = 'tabby';
console.log(url.href); // "http://www.example.com/cats#tabby"

URLs will be encoded as per RFC 3986:

url.pathname = 'démonstration.html';
console.log(url.href); // "http://www.example.com/d%C3%A9monstration.html"

The URLSearchParams interface can be used to build and manipulate the URL query string.

To get the search params from the current window's URL, you can do this:

// https://some.site/?id=123
var parsedUrl = new URL(window.location.href);
console.log(parsedUrl.searchParams.get("id")); // 123

The stringifier method of URL is the href property, so the constructor can be used to normalise and encode a URL directly.

const response = await fetch(new URL('http://www.example.com/démonstration.html'));


Creates and return a URL object composed from the given parameters.


Is a DOMString containing a '#' followed by the fragment identifier of the URL.
Is a DOMString containing the domain (that is the hostname) followed by (if a port was specified) a ':' and the port of the URL.
Is a DOMString containing the domain of the URL.
Is a DOMString containing the whole URL.
URL.origin Read only
Returns a DOMString containing the origin of the URL, that is its scheme, its domain and its port.
Is a DOMString containing the password specified before the domain name.
Is a DOMString containing an initial '/' followed by the path of the URL.
Is a DOMString containing the port number of the URL.
Is a DOMString containing the protocol scheme of the URL, including the final ':'.
Is a DOMString containing a '?' followed by the parameters of the URL.
URL.searchParams Read only
Returns a URLSearchParams object allowing to access the GET query arguments contained in the URL.
Is a DOMString containing the username specified before the domain name.

The URL interface implements methods defined in URLUtils.

Returns a DOMString containing the whole URL. It is a synonym for URLUtils.href, though it can't be used to modify the value.
URL.toJSON() [available since FireFox v54]
Returns a DOMString  containing the whole URL. It returns the same string as the href property.

Static methods

Returns a DOMString containing a unique blob URL, that is a URL with blob: as its scheme, followed by an opaque string uniquely identifying the object in the browser.
Revokes an object URL previously created using URL.createObjectURL().


Specification Status Comment
File API
The definition of 'URL' in that specification.
Working Draft Added the static methods URL.createObjectURL() and URL.revokeObjectURL().
The definition of 'API' in that specification.
Living Standard Initial definition (implements URLUtils).

Browser compatibility

We're converting our compatibility data into a machine-readable JSON format. This compatibility table still uses the old format, because we haven't yet converted the data it contains. Find out how you can help!

Feature Chrome Edge Firefox (Gecko) Internet Explorer Opera Safari
Basic support 8.0[2]


4.0 (2.0)[1][3][6]
19.0 (19.0)
No support[4] 15.0[2]
username, password, and origin 52 10240 26.0 (26.0) ? 19 (Yes)
searchParams 51 No support[5] 29.0 (29.0) ? 36 No support
toJSON ? ? 54 (54) ? ? ?
Feature Android Webview Chrome for Android Firefox Mobile (Gecko) IE Mobile Opera Mobile Safari Mobile
Basic support 4[2]
14.0 (14.0)[1][3][6]
19.0 (19.0)
(Yes) 15.0[2] 6.0[2]
username, password, and origin 52 52 26.0 (26.0) ? ? (Yes)
searchParams 51 51 29.0 (29.0) ? ? ?

[1] From Gecko 2 (Firefox 4) to Gecko 18 included, Gecko supported this interface with the non-standard nsIDOMMozURLProperty internal type. As the only to access such an object was through window.URL, in practice, this didn't make any difference.

[2] This feature is implemented under the non-standard name webkitURL.

[3] For Firefox, to use from chrome code, JSM and Bootstrap scope, you have to import it like this:


URL is available in Worker scopes.

[4] As of IE11, instantiating new URL objects is not supported - ie. new URL() does not work. 

[5] see status of URL API in Microsoft Edge, API Catalog of Microsoft Edge and https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6263638-url-api.

[6] Firefox has a bug whereby single quotes contained in URLs are escaped when accessed via URL APIs (bug 1386683). This has been fixed as of Firefox 57.

See also

문서 태그 및 공헌자

이 페이지의 공헌자: yuj25
최종 변경: yuj25,