This project is not covered by Drupal’s security advisory policy.
xmlrpc_page_load Provides a simple XMLRPC call that can simulate a page being accessed as a certain user. This can be used in two ways:
To simulate accessing a page when other mechanisms prevent a traditional user login
To seed caches by having apache / nginx handle the request as if someone actually accessed the site
HTTPRL Spider has been modified to support this project so you can effectively create drupal sites that not only spider themselves, but do so against all user accounts / roles! Because it's making the call out and wrapping around, this allows even cache bin mechanisms like APCu and memory based cache bins to be utilized for pages. This also complements Authcache well in Drupal 7 because it can seed specific user accounts.
For security, this function can only be tripped if either the drupal_private_key for the site is used or an equivalent private value. This makes it really easy for httprl to hook it up when on the same box but also allows for secure remote connections. The pages are also only simulated loads in that all "printing" and http header delivery has been sanitized. This means Drupal thinks it just loaded a fully bootstrapped page to user 10 (for example) but user 10 wasn't logged in, and the page never went anywhere, and all the person that kicks this job off gets is a "yup, I rendered the page".
Project information
- Maintenance fixes only
Considered feature-complete by its maintainers. - Module categories: Administration Tools, Developer Tools, Performance
- 2 sites report using this module
- Created by btopro on , updated
- This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.