Url Tracker omits the root slash from the path, which is confusing and doesn't conform to the standard.
Any chance of allowing full paths?
Current:
some/page/
Better:
/some/page/
Technical information: according to the RFC http://www.w3.org/Addressing/URL/url-spec.txt, a path is what follows the domain name (and optionally the port number) and starts with a /. Other RFCs follow the same syntax.
Layer 7 Application Delivery Controllers (e.g. F5's BIG-IP LTM etc.) also follow the syntax in which a path starts with a /.
Note: even when a client (e.g. browser) doesn't show the / after the domain name, the path that is sent (and therefore received by the server) does include it.
Paths should start with a slash (/)
Url Tracker omits the root slash from the path, which is confusing and doesn't conform to the standard.
Any chance of allowing full paths?
Current:
some/page/
Better:
/some/page/
Technical information: according to the RFC http://www.w3.org/Addressing/URL/url-spec.txt, a path is what follows the domain name (and optionally the port number) and starts with a /. Other RFCs follow the same syntax.
Layer 7 Application Delivery Controllers (e.g. F5's BIG-IP LTM etc.) also follow the syntax in which a path starts with a /.
Note: even when a client (e.g. browser) doesn't show the / after the domain name, the path that is sent (and therefore received by the server) does include it.
This is just a UI change and not that big of a deal in my opinion, but thanks for your suggestion.
I changed my mind while working on the UrlTracker. I agree with you that it looks kind of silly, so I fixed it and it will be included in v3 :-)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.