Beagle v1.6 is no longer actively maintained. The documented version you are viewing may contain deprecated functionality. For up-to-date documentation, see the latest version .
Most elements from Beagle make use of a field to define the URLs. This field is sent to backend to indicate HTTP requests that an application needs to do and that are managed by Beagle’s client.
You have two ways to use these paths on Beagle:
A type of path used when you want to ignore the base URL already configured in your frontend application. If you make this indication, Beagle will understand that the URL is already complete and it will use it like this:
Example of absolute path:
A type of path used when you decide to keep the base URL configured in your frontend application.
For example, if you define a base URL like
https://api.zup.com.br/my-bff and receive a relative path somewhere like
/ home, Beagle will create the complete URL like
https://api.zup.com. br /my-bff/home.
Beagle uses the Encoding type RFC 3986 standard when handling URLs.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.