Current behavior expects the developer to either specify an entire hostname (http://backend.com/users) or use a wildcard (*/users) to handle request URI.
It's familiar to developers to specify routes with a leading slash and expecting the hostname to be matched implicitly.
When provided the route /users MSW would match any /users requests that are fired from the _current page's hostname_:
http://localhost:8080/usersHowever, it won't match the same paths from the different hostname:
https://api.dev.backend/usersPerfect. Thank you!
@kentcdodds thank you for illustrating how confusing this gets in your stream. This should be a trivial change.
Released in 0.5.1. Examples in the documentation were updated to use the leading slash without a wildcard, where applicable.