Exercise 2: Why the Glob Segment Needs No Separate Regex — Possible Solution
====================================================================

WHAT THE GLOB SEGMENT DOES
------------------------------
Per this chapter, get '*path', to: 'pages#show' uses a segment prefixed with * directly inside the route pattern string to capture every remaining part of the URL path, including any slashes it contains, into params[:path].

WHY NO SEPARATE REGEX IS NEEDED
------------------------------
Per this chapter, the * glob syntax is already slash-aware as part of Rails' own route-pattern syntax itself - it's built directly into what the * prefix means in a route string, with no additional constraint required to make it match multiple path segments. Laravel's own wildcard route, by contrast, used an optional {path?} segment that needed an explicit ->where('path', '.*') regex constraint added afterward specifically to make it match slashes, since Laravel's own default wildcard segment behavior doesn't span slashes without that extra constraint.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains what the *path glob segment captures, and correctly explains that its slash-spanning behavior is built into the glob syntax itself, unlike Laravel's wildcard route, which needed a separate regex constraint added to achieve the same result.