Hi,
I'm familiar with role of profile in the OSRM processing flow
as well as descriptions regarding profile and {profile} parameter
in the HTTP API docs.
Still. I'm not entirely clear about the profile role in the HTTP API URLs.
My current understanding is this:
1. profile is actively used duri
Hi Mateusz,
The in the URL is an unused string. It's there for future
compatibility if we ever add multiple-profile support to OSRM, but osrm-routed
does not look at it currently, other than to ensure that it's there.
Quite a few people use it as a reverse-proxy filtering token - run a re
