Drupal RSS视图如何通过URL GET参数访问？添加token后无法显示

Hey there! Sorry to hear your RSS feed is breaking when you add that token parameter. Let's walk through some practical solutions to fix this, including the filter approach you mentioned.

First, Understand Why the Parameter is Breaking the Feed #

Most RSS feed generators (especially in CMS platforms like Drupal, WordPress, etc.) are strict about which GET parameters they recognize. If you append an unexpected param like token, the system might either ignore it and return an invalid feed, or reject the request entirely.

First, confirm that removing the token brings back the working feed (you probably already did this, but it's good to double-check). Then take a look at the original feed URL to see what parameters it expects (like ?type=rss or similar)—this helps ensure we don't interfere with required values.

Solution 1: Implement a Token Validation Filter (Recommended) #

Since you're okay with hardcoding the token, adding a filter/middleware layer is the cleanest, most maintainable approach. This checks for the valid token before serving the feed, and ensures the parameter doesn't disrupt the feed generation.

For Drupal (matches your /taxonomy/feed URL structure) #

Create a custom module or add this code to an existing one:

// In your custom module's .module file
function my_custom_module_feed_access() {
  $valid_token = 'tJHqoIaixc'; // Your hardcoded token
  if (isset($_GET['token']) && $_GET['token'] === $valid_token) {
    return TRUE;
  }
  return FALSE;
}

// Hook into the taxonomy feed route to add access control
function my_custom_module_route_alter(&$routes) {
  if (isset($routes['taxonomy_term_feed'])) {
    $routes['taxonomy_term_feed']->setRequirement('_custom_access', 'my_custom_module_feed_access');
  }
}

This will validate the token before serving the feed. If the token is correct, the feed loads normally; if not, access is denied.

For WordPress #

Add this to your theme's functions.php file or a custom plugin:

function validate_feed_token($query_vars) {
  $valid_token = 'tJHqoIaixc';
  // Check if we're accessing a feed and the token is present
  if (isset($query_vars['feed']) && isset($_GET['token'])) {
    if ($_GET['token'] !== $valid_token) {
      wp_die('Invalid token');
    }
  }
  return $query_vars;
}
add_filter('request', 'validate_feed_token');

This ensures the token is validated without interfering with the feed's required parameters.

Solution 2: Modify the Feed Script Directly #

If you have direct access to the feed's underlying script (e.g., the PHP file generating the RSS), add a token check at the very top:

// At the start of your feed generation script
$valid_token = 'tJHqoIaixc';
if (!isset($_GET['token']) || $_GET['token'] !== $valid_token) {
  header('HTTP/1.1 403 Forbidden');
  exit('Access denied');
}

// Proceed with generating the RSS feed as usual

Note: This is simple but less maintainable if you're using a CMS that might overwrite core files during updates. Stick to filters/modules where possible.

Solution 3: Use URL Rewriting (Apache/Nginx) #

If you prefer not to modify code, use server rewrite rules to validate the token and strip it before passing the request to the feed script.

Apache (in .htaccess) #

RewriteEngine On
# Allow access only if the correct token is present
RewriteCond %{QUERY_STRING} !token=tJHqoIaixc [NC]
RewriteRule ^taxonomy/feed$ - [F,L]

# Strip the token parameter so the feed script doesn't see it
RewriteCond %{QUERY_STRING} token=tJHqoIaixc [NC]
RewriteRule ^taxonomy/feed$ /taxonomy/feed? [L]

Nginx #

location /taxonomy/feed {
  if ($arg_token != "tJHqoIaixc") {
    return 403;
  }
  # Strip the token parameter before passing to the feed script
  rewrite ^/taxonomy/feed$ /taxonomy/feed? break;
  # Add your usual proxy/fastcgi pass directive here
}

Final Testing Tips #

• After implementing any solution, test the feed with the correct token (should load normally) and without (should return a 403 or error).
• If you're using a CMS, avoid modifying core files—stick to hooks, modules, or plugins to prevent issues during updates.

内容的提问来源于stack exchange，提问作者Jason Derrick