Advanced URL Parameter Usage in Custom Auto-Responders

In addition to custom parameters, the auto-responder system supports several default URL properties that can be used in your return URLs. These properties provide powerful flexibility when constructing your custom responses.

Default URL Properties

When constructing your return URL, you can use the following default properties, enclosed in curly braces {}:

• {protocol}: The protocol of the URL (e.g., "http:" or "https:")
• {host}: The full hostname, including subdomains
• {hostname}: The domain name without subdomains
• {port}: The port number, if specified
• {pathname}: The path of the URL after the domain
• {search}: The query string, including the leading "?"
• {hash}: The fragment identifier, including the leading "#"
• {href}: The full, original URL

Using Default Properties in Return URLs

These properties can be extremely useful for maintaining parts of the original URL structure or for constructing more dynamic return URLs.

Example:

Detect URL:

https://www.youtube.com/watch?v=:videoId

Return URL:

https://www.youtube-nocookie.com/embed/{videoId}{search}

In this example, {search} will include any additional query parameters from the original URL, allowing you to preserve things like timestamps or playlist information.

Combining Custom and Default Properties

You can mix and match custom parameters (like :videoId) with default properties for maximum flexibility:

Detect URL:

https://:subdomain.example.com/:category/:id

Return URL:

https://embed.{hostname}/{category}/{id}?original={href}

This setup would:

1. Capture the custom :category and :id parameters
2. Use the {hostname} to maintain the original domain (without the subdomain)
3. Include the full original URL as a query parameter using {href}

Advanced Usage Tips

1. Pathname Manipulation: You can use {pathname} to keep the entire path structure and combine it with other elements:

   https://newdomain.com{pathname}?source=original
   

2. Query String Preservation: Use {search} to keep all original query parameters:

   https://embed.example.com/video/{videoId}{search}
   

3. Full URL Encoding: When using {href}, consider URL encoding it if you're using it as a parameter:

   https://archive.org/wayback?url={href}
   

4. Protocol Switching: Use {protocol} to maintain or switch protocols dynamically:

   {protocol}//embed.{hostname}/view/{id}
   

By leveraging these default URL properties along with custom parameters, you can create highly sophisticated and flexible auto-responder configurations that can handle a wide variety of URL structures and use cases.

Remember to test your configurations thoroughly, as the behavior might vary slightly depending on the exact structure of the incoming URLs.