Read this ^
Find a property Search Prop redirect
Add under charset utf8:
Create a domain alias in Forge
Create actual domain first and upload git repo
Create a domain alias - don't add a new repo, leave it blank.
Edit the nginx file and look for (currently on line 8):
Update this to root to your real domain
*note: DO NOT set the URL above as https, but DO set it as httpS in the admin area of search prop
If two search props use this htaccess and put in the root
For the redirect to work you cannot have a real folder in place that the re-write is trying to act on
"find-a-property folder was taking priority. Moving it out the way fixed the issue"
Microsoft Server (IIS) Settings:
Reverse Proxy with URL Rewrite v2 and Application Request Routing:
1: Enabling Reverse Proxy functionality
2. Create the rewrite rule.
Below is an example rule set for loading a search-prop onto the url: http://example.com/property-search
3. Check routing is working
Once 1 & 2 are complete, you should be able to go to: http://example.com/property-search and they will see the property search.
4. Important! Link rewrites
To overcome this issue please let your contact at agentsinsight know that you are ready to have the links set to the live domain. We will then toggle these so links keep the end-user on the http://example.com/property-search website.