I'm encountering a perplexing situation that is entirely new to me and difficult to comprehend. I find myself unable to decipher what exactly I am witnessing, leading to uncertainty about why it is occurring, not to mention the challenge of determining how to resolve it.
Within my angular application, I have implemented a route as follows:
const routes: Routes = [
{ path: "beep", component: BeepComponent },
{ path: "**", component: LandingComponent }
];
The baffling aspect arises when accessing it through the browser (localhost:4200/beep) results in proper rendering. However, attempting the same request in Postman yields an unexpected outcome shown below.
<!DOCTYPE html>
<html lang="en><
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot GET /beep</pre>
</body>
</html>
What might this behavior signify? If unclear, how can I delve deeper into troubleshooting this issue? (The fact that such a scenario occurs has caught me off guard...)
Furthermore, upon running the page on Azure, a momentary 404 error appears before vanishing. This peculiar sequence seems to indicate the initial call fails (Not Found) followed by another request initiating (clearing the Network tab). Although I suspect resolving the Postman query will remedy this, for now, I am concentrating my efforts there.