URLのリダイレクトと書き換え
定義した条件に基づいて、ネットワーク リクエストを別のURLへリダイレクトしたり、URLの一部を書き換えたりする方法を学びます。
「URLのリダイレクトと書き換え」はCoddyKit上の無料Browser Extensions Development (Chrome & Edge)レッスンです。 これはレッスン3/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはBrowser Extensions Development (Chrome & Edge)学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Browser Extensions Development (Chrome & Edge)コースには全4レッスンが含まれています。
このレッスンの一部はまだ翻訳されておらず、英語で表示されています。
Intro to URL Magic
Welcome! In this lesson, we'll learn how browser extensions can change where network requests go or how their URLs look.
- Redirecting sends a request to a completely different URL.
- Rewriting modifies parts of the original URL before it's processed.
Both are powerful tools for controlling web traffic using the `declarativeNetRequest` API.
Why Redirect or Rewrite?
Modifying URLs can serve many useful purposes:
- Enforce HTTPS: Automatically upgrade insecure HTTP connections.
- Fix broken links: Redirect old URLs to new ones.
- Clean up URLs: Remove unnecessary tracking parameters.
- Block unwanted content: Redirect specific requests to an empty page.
It helps improve security, privacy, and user experience.
The `redirect` Action Type
To redirect a network request, we use the `redirect` action type in our `declarativeNetRequest` rules. This action specifies a new URL or a pattern to generate one.
Here's a basic structure for a redirect rule:
{
"id": 1,
"priority": 1,
"action": {
"type": "redirect",
"redirect": {
"url": "https://new-example.com"
}
},
"condition": {
"urlFilter": "https://old-example.com/*"
}
}Simple URL Redirect Example
Let's say you want to redirect all requests to an old blog post URL to a new one. This rule tells the browser: 'If you see a request for old-blog.html, send it to new-blog-post.html instead.'
[
{
"id": 1,
"priority": 1,
"action": {
"type": "redirect",
"redirect": {
"url": "https://www.example.com/new-blog-post.html"
}
},
"condition": {
"urlFilter": "https://www.example.com/old-blog.html"
}
}
]Enforcing HTTPS with Redirects
A common use case is to ensure secure connections. You can redirect all HTTP requests for a specific domain to their HTTPS equivalent. This enhances user security by encrypting data.
This rule redirects any HTTP request for example.com to its HTTPS version.
[
{
"id": 2,
"priority": 1,
"action": {
"type": "redirect",
"redirect": {
"transform": {
"scheme": "https"
}
}
},
"condition": {
"urlFilter": "http://example.com/*",
"resourceTypes": ["main_frame", "sub_frame", "script", "image", "stylesheet"]
}
}
]Introducing `regexSubstitution`
Sometimes you don't want to redirect to a fixed URL, but rather modify parts of the original URL. This is where regexSubstitution comes in. It uses regular expressions to match and replace parts of the URL.
The matched parts from the regexFilter in the condition can be referenced in the substitution string using backreferences like \1, \2, etc.
Rewriting URL Paths Example
Imagine you have old URLs like /users/123 and want them to become /profile/123. You can use regexSubstitution to capture the ID and rewrite the path.
This rule captures the number after /users/ and reuses it in the /profile/ path.
[
{
"id": 3,
"priority": 1,
"action": {
"type": "redirect",
"redirect": {
"regexSubstitution": "https://www.example.com/profile/\\1"
}
},
"condition": {
"regexFilter": "^https://www.example.com/users/([0-9]+)$",
"resourceTypes": ["main_frame"]
}
}
]Modifying Query Parameters
regexSubstitution is great for cleaning up query parameters. You might want to remove a specific tracking parameter, like utm_source, from URLs to improve privacy or simplify sharing.
This rule matches URLs with ?utm_source=... and removes that parameter, keeping everything else.
[
{
"id": 4,
"priority": 1,
"action": {
"type": "redirect",
"redirect": {
"regexSubstitution": "\\1"
}
},
"condition": {
"regexFilter": "^(https?://[^?]+)\\?utm_source=[^&]*(?:&(.*))?$",
"resourceTypes": ["main_frame"],
"excludedInitiatorDomains": ["example.com"]
}
}
]Match Patterns & Regular Expressions
Remember, `urlFilter` uses match patterns, which are simpler for basic matches. `regexFilter` requires full regular expressions and is used when you need to capture parts of the URL for `regexSubstitution`.
- Match Patterns: Wildcards like
*, specific schemes/hosts. - Regular Expressions: Powerful pattern matching with groups
()and special characters.
Choose the right tool for the job!
Redirect Challenge
Consider a rule designed to redirect all requests from http://insecure.com to https://secure.com. Which `redirect` action type is best suited for this goal?
Recap: Redirects & Rewrites
Great job! You've learned how to powerfully control network requests:
- Redirects: Send requests to entirely new URLs using `redirect` with a `url`.
- Rewrites: Modify parts of URLs using `redirect` with `transform` or `regexSubstitution`.
- HTTPS enforcement: A practical use of `transform` to upgrade connections.
- URL cleaning: Use `regexSubstitution` to remove or change parameters.
These techniques allow you to enhance security, fix issues, and customize user browsing experiences.
よくある質問
「URLのリダイレクトと書き換え」レッスンは無料ですか？
はい。「URLのリダイレクトと書き換え」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Browser Extensions Development (Chrome & Edge)コースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Browser Extensions Development (Chrome & Edge)コースには全4レッスンが含まれています。
「URLのリダイレクトと書き換え」で何を学びますか？
定義した条件に基づいて、ネットワーク リクエストを別のURLへリダイレクトしたり、URLの一部を書き換えたりする方法を学びます。 ブラウザで直接実行するハンズオンコードでBrowser Extensions Development (Chrome & Edge)を演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。
Browser Extensions Development (Chrome & Edge)を始めるのに経験は必要ですか？
事前経験は必要ありません。CoddyKitのBrowser Extensions Development (Chrome & Edge)は初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン3/4です。
「URLのリダイレクトと書き換え」レッスンにはどのくらい時間がかかりますか？
ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。
このBrowser Extensions Development (Chrome & Edge)レッスンでコードを書いて実行できますか？
はい。すべてのBrowser Extensions Development (Chrome & Edge)レッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。