Domain Forwarding Paths and Parameters | Webnames.ca Help Center

As part of our URL forwarding, paths and parameters can be retained and passed along to the destination URL. The most notable aspect of configuring your forwarding is how/when the training slash is included in the destination URL.

Below are some examples.

Configured Destination	Client Browses To	Client is Redirected To	Notes
http://destination.com	http://source.com	http://destination.com	Basic domain forwarding; no path or query in the client requested URL
http://destination.com/	http://source.com/sub/path/doc.htm?param=val#anchor	http://destination.com/sub/path/?param=val#anchor	Destination URL had a trailing slash, so client sub paths are appended properly
http://destination.com/dest/path	http://source.com	http://destination.com/dest/path	Basic domain forwarding; destination URL path preserved
http://destination.com/dest/path	http://source.com/	http://destination.com/dest/path	Basic domain forwarding; destination URL path preserved
http://destination.com/dest/path/	http://source.com	http://destination.com/dest/path	Basic domain forwarding; destination URL path preserved
http://destination.com/dest/path/	http://source.com/sub/path/	http://destination.com/dest/path/sub/path/	Request path and query always appended, even if destination URL already has them; possible 404 depending on web server folders/routing
http://destination.com/dest/path/?param=val	http://source.com	http://destination.com/dest/path/?param=val	Destination URL includes a query (the part after the "?" character). Path and query still appended, but target web server will usually ignore
http://destination.com/dest/path/?param=val	http://source.com/	http://destination.com/dest/path/?param=val	Destination URL includes a query (the part after the "?" character). Path and query still appended, but target web server will usually ignore
http://destination.com	http://source.com/sub/path/doc.htm?param=val#anchor	http://destination.comsub/path/?param=val#anchor	Request path and query always appended, even if destination URL already has them; will cause 404 not found due to lack of trailing slash causing invalid domain name
http://destination.com/dest/path	http://source.com/sub/path/doc.htm?param=val#anchor	http://destination.com/dest/pathsub/path/?param=val#anchor	Request path and query always appended, even if destination URL already has them; probable 404 not found depending on web server folders/routing
http://destination.com/dest/path/	http://source.com/sub/path/doc.htm?param=val#anchor	http://destination.com/dest/path/sub/path/doc.htm?param=val#anchor	Request path and query always appended, even if destination URL already has them; possible 404 depending on web server folders/routing
http://destination.com/dest/path/?param=val	http://source.com/sub/path/doc.htm?param=val#anchor	http://destination.com/dest/path/?param=valsub/path/doc.htm?param=val#anchor	Destination URL includes a query (the part after the "?" character). Path and query still appended, but parameter value corrupted due to lack of trailing "&" character; possible 404 not found
http://destination.com/dest/path/?param=val&	http://source.com/sub/path/doc.htm?param=val#anchor	http://destination.com/dest/path/?param=val&sub/path/doc.htm?param=val#anchor	Destination URL includes a query (the part after the "?" character). Path and query still appended, but parameter value preserved due to trailing "&" character
http://destination.com/?	http://source.com/sub/path/doc.htm?param=val#anchor	http://destination.com/?sub/path/doc.htm?param=val#anchor	Same as above, but the single trailing "?" character will cause most web servers to ignore the path