• Hello,

    When our blog site was first created, we downloaded the WordPress files under the URL structure https://dev.blog.store.nationalgeographic.com/ . Then we implemented a reverser proxy which changed our URL structure to https://shopdev.nationalgeographic.com/blog and moved our WordPress files under the subdirectory /blog.

    On the new URL (shopdev.nationalgeographic.com/blog) our post, pages and page pagination are not displaying the correct content.

    On our “About” page, it displays a list of post we have published and on the title tab for the page its says “page not found”. Its suppose to display content we wrote that pertains to our organization.

    When you click on a post, it displays a list of posts we have published and doesn’t actually display the content of the post.

    The page pagination link is suppose to allow users to navigate between the posts we’ve published but instead it lead to a 404 page.

    After implementing the reverse proxy, was there a WordPress file we needed to update?

    Please advice on how to fix this issue.

    Thank you in advance!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    The problem is that the URLs generated by https://dev.blog.store.nationalgeographic.com/ are different than https://shopdev.nationalgeographic.com/blog so links will be broken.

    Possibly, I could not resolve the second URL and take a look at the HTML.

    What are you using for that reverse proxy? Can it also perform content re-writing such as what you can use via mod_substitute?

    https://httpd.apache.org/docs/2.2/mod/mod_substitute.html

    Edit: But this URL works really well for me. https://blog.store.nationalgeographic.com/

    Thread Starter mjaji

    (@mjaji)

    Hi Jan,

    Thank you for your response! We used apache for the reverse proxy. If we’re able to perform content re-writing such as what you can use via mod_substitute, what affect will the change have? Will it solve the URL generation issue?

    You are unable to access the second url https://shopdev.nationalgeographic.com/blog because its our development site which currently can only be accessed on our network.

    The URL https://blog.store.nationalgeographic.com/ is our current production environment which eventually will undergo a reverse proxy as well and the new URL structure will be shop.nationalgeographic.com/blog We are currently testing on our dev site first to make sure everything works properly before pushing it live to our production site.

    If there are any additional information you’ll need please let me know.

    Thanks in advance!

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    We used apache for the reverse proxy.

    That cheers me immensely, Apache modules and their config can be fun. ??

    If we’re able to perform content re-writing such as what you can use via mod_substitute, what affect will the change have? Will it solve the URL generation issue?

    It should let you modify the HTML before it serves the content.

    This is actually the sort of problem that I like to play with but I’m away (really away) and don’t think this is something I can play with while traveling. The idea I have is that whenever mod_substitute sees https://dev.blog.store.nationalgeographic.com/ it will modify that to https://shopdev.nationalgeographic.com/blog. That ought to work for any regular http pages (should not work for https).

    That may be overkill though but I’m traveling and it’s one idea. ??

    Thread Starter mjaji

    (@mjaji)

    Hi Jan,

    What are some of the pros and cons for mod_substitute? Is the change reversible? Is there another alternative we can take that’s similar to mod_substitute? Any plugins?

    Thanks in advance!

    Thread Starter mjaji

    (@mjaji)

    Hi Jan,

    What are some of the pros and cons for mod_substitute? Is the change reversible? Is there another alternative we can take that’s similar to mod_substitute? Any plugins?

    Thanks in advance!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Moving content to new URL structure after reverse proxy change’ is closed to new replies.