대부분의 홈페이지는 모바일 지원을 한다.
pc에서 모바일 페이지를 보고 싶을 경우가 있는데 이럴때 사용하면 좋은 extention이 있다.
User-Agent Switcher for Chrome
https://chrome.google.com/webstore/detail/user-agent-switcher-for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg
설치를 하면 우측 상단에 browser action이 생기는데 누르면 지원하는 agent를 설정 할 수 있다.
android , iphone 등을 선택하면 현재 browser 모드가 설정되고 google.com 에 접속하면 모바일 모드로 보이는 것을 확인 할 수 있다.
chrome exteion을 이용한 것인데 아래 코드로 동작하는 것을 확인 하였다.
요청 하기전 설정된 정보로 User-Agent 헤더 정보를 바꾼다.
function updateListeners() {
if (!listener) {
listener = function(details) {
var header_map = {
requestHeaders : details.requestHeaders
};
if (details && details.url && details.requestHeaders
&& details.requestHeaders.length > 0) {
header_map = {
requestHeaders : replaceHeader(getCacheSpoofValues(
details.url, details.tabId), details.requestHeaders)
}
}
return header_map
}
}
chrome.webRequest.onBeforeSendHeaders.addListener(listener, {
"urls" : [ "http://*/*", "https://*/*" ]
}, [ "requestHeaders", "blocking" ])
}
https://developer.chrome.com/extensions/webRequest
chrome.webRequest
request 요청중의 관찰, 트래픽분석, blocking ,intercept 할 때 사용한다.
사용시 아래 권한을 준다.
{
"name": "My extension",
...
"permissions": [
"webRequest",
"*://*.google.com/"
],
...
}
request의 라이브사이클 onBeforeSendHeaders 2번째 단계 이다.
onBeforeRequest (optionally synchronous)Fires when a request is about to occur. This event is sent before any TCP connection is made and can be used to cancel or redirect requests.onBeforeSendHeaders (optionally synchronous)Fires when a request is about to occur and the initial headers have been prepared. The event is intended to allow extensions to add, modify, and delete request headers (*). The onBeforeSendHeaders event is passed to all subscribers, so different subscribers may attempt to modify the request; see the Implementation details section for how this is handled. This event can be used to cancel the request.onSendHeadersFires after all extensions have had a chance to modify the request headers, and presents the final (*) version. The event is triggered before the headers are sent to the network. This event is informational and handled asynchronously. It does not allow modifying or cancelling the request.onHeadersReceived (optionally synchronous)Fires each time that an HTTP(S) response header is received. Due to redirects and authentication requests this can happen multiple times per request. This event is intended to allow extensions to add, modify, and delete response headers, such as incoming Set-Cookie headers. The caching directives are processed before this event is triggered, so modifying headers such as Cache-Control has no influence on the browser's cache. It also allows you to redirect the request.onAuthRequired (optionally synchronous)Fires when a request requires authentication of the user. This event can be handled synchronously to provide authentication credentials. Note that extensions may provide invalid credentials. Take care not to enter an infinite loop by repeatedly providing invalid credentials.onBeforeRedirectFires when a redirect is about to be executed. A redirection can be triggered by an HTTP response code or by an extension. This event is informational and handled asynchronously. It does not allow you to modify or cancel the request.onResponseStartedFires when the first byte of the response body is received. For HTTP requests, this means that the status line and response headers are available. This event is informational and handled asynchronously. It does not allow modifying or cancelling the request.onCompletedFires when a request has been processed successfully.onErrorOccurredFires when a request could not be processed successfully.
