5. 그럼 모두 HTTPS로 바꾸면 ?
• https(SSL)의 성능 문제.
• ssl handshake, 데이터 암호화/복호화 등에 따른 비용 추가.
• 서버의 CPU 사용량 증가.
• http 대비 현저히 낮은 TPS.
• 따라서, 꼭 필요한 곳에서만 https 사용이 필요.
6. 다른 방법. 단지 SLASH 두개만 !
• 사용자가 http로 접속하든, https로 접속하든 알아서 변경하여 요청.
• 브라우져의 보안경고창 회피.
• <img src=”//example.com/img/logo.png” alt=”” />
• <script type=”text/javascript” src=”//code.jquery.com/jquery-1.8.0.min.js” />
• <link rel="stylesheet" href="//example.com/css/layout.css" type="text/css" media="all" />
7. RFC 3986
• 4.2. Relative Reference
A relative reference takes advantage of the hierarchical syntax (Section 1.2.3) to express a URI reference
relative to the name space of another hierarchical URI.
relative-ref = relative-part [ "?" query ] [ "#" fragment ]
relative-part = "//" authority path-abempty
/ path-absolute
/ path-noscheme
/ path-empty
The URI referred to by a relative reference, also known as the target URI, is obtained by applying the
reference resolution algorithm of Section 5.
A relative reference that begins with two slash characters is termed a network-path reference; such references
are rarely used. A relative reference that begins with a single slash character is termed an absolute-path
reference. A relative reference that does not begin with a slash character is termed a relative-path reference.
A path segment that contains a colon character (e.g., "this:that") cannot be used as the first segment of a
relative-path reference, as it would be mistaken for a scheme name. Such a segment must be preceded by a dot-
segment (e.g., "./this:that") to make a relative-path reference.
• http://tools.ietf.org/html/rfc3986#section-4.2
