This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Trying to set up Site Path Routing - end up getting 404 errors

Hello everyone here.  Please help with advice and ideas
I have a tough task of crossbreeding 2 websites based on 2 different technology stacks.
I have website 1 a.k.a https://www.abc.com which is running on WordPress on LAMP server and this is the public website.
I have website 2 a.k.a https://commerce.abc.com and this is a custom developed ecommerce system running on IIS, the whole application is written in VB.NET.
My intention is to make website 2 to open within the context path of website 1 so it looks to the visitors like website 2 is running inside the website 1; something like https://www.abc.com/commerce
With this plan I set up Site Path Routing in the following manner:
 
Site Path Routing
 
My problem is that when I access website 1 everything is good, but once I add manually the path https://www.abc.com/commerce I get 404 error suggesting that website 1 does not have such path.  For the sake of experiment I tried creating a folder ‘commerce’ inside website 1 and disabling the SPR rule but then the error naturally changes to 403 Forbidden suggesting that I am not allowed to browse the folders.

My question – what am I doing wrong about site path routing setup?  Is what I am trying to do achievable?



This thread was automatically locked due to age.
Parents Reply
  • Hello, Dirk.

    Thanks for suggestion. 

    Do you mean a separate path route should be set up in UTM or you mean on the real webserver https://commerce.abc.com I should have a folder under the site root like application_folder/commerce?  I am confused.

    I tried adding a folder 'commerce' inside the application folder which should not have any impact and it did not other than throwing a 403 Error since there is no default document in the folder.

     

    If you mean that it should be a site path route in UTM then I don't know how to do it.

    site 1: https://www.abc.com should hit the default page of the site 1

    site 1: https://www.abc.com/commerce should open the default page of the site 2 in the context path of site 1

    So, what kind of route should I write for https://commerce.abc.com ?

    Thanks

     

     

     

Children
  • Dirk,

    I made an additional path route which looks like this

    Virtual Web Server: https://commerce.abc.com

    Path: /commerce

    Real Web Server: Real Webserver for Virtual Server 2

    However I still get the same 404 errors, so my source server (Webserver 1) is still trying to locate an non-existent folder in its file system, which I believe, means site path routing instruction has no effect on Webserver 1.  What do you think?

     

  • with Path: /commerce --> Real WebServer 2    the Webserver 1 should not show you access.

    Please give us some screenshots from virtual ws, real ws and sitepath settings.


    Dirk

    Sophos Solution Partner since 2003
    If a post solves your question click the 'Verify Answer' link.