Make WordPress Core

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#50157 closed defect (bug) (duplicate)

HTTP_HOST instead of configuration value

Reported by: jschodermedikura's profile jschodermedikura Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: administration Cc:

Description (last modified by SergeyBiryukov)

We are using an usual setup and run into an issue with the page pagination inside the admin-pages.

Only parts of our website is created in WordPress, some parts are created in NodeJS. So we are using a proxy to delegate all our requests from our live url (https://live.medikura.com) to our hosted wordpress (https://hosted.medikura.com)

We changed both configuration values (wordpress url + website url) to our live page (https://live.medikura.com). In almost all cases this works perfectly fine. But we have a problem when it comes to pagination which uses /wp-admin/includes/class-wp-list-table which doesn't use any configuration value but the PHP variable $_SERVER['HTTP_HOST'] which of course is our hosted url (https://hosted.medikura.com) This means as soon as a user tries to click next on the pagination she is redirected to our hosting url which in turn redirects to our live url and forces a new login.

Can you please make sure that the code always uses either of the configuration values instead of the non configurable $_SERVER['HTTP_HOST'].

Thx :-)

Change History (2)

#1 @ocean90
4 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed
  • Version 5.4.1 deleted

Hello @jschodermedikura, welcome to WordPress Trac!

Thanks for the report, we're already tracking this issue in #36201.

Note that you can configure/override $_SERVER['HTTP_HOST'] with any domain in wp-config.php for example.

#2 @SergeyBiryukov
4 years ago

  • Description modified (diff)
Note: See TracTickets for help on using tickets.