fix: handle non-success HTTP status codes in URL inspection like any other (#70)

* Initial plan for issue

* Initial assessment and plan for handling non-success status codes

Co-authored-by: serhalp <[email protected]>

* Fix $fetch to handle non-success status codes and add test coverage

Co-authored-by: serhalp <[email protected]>

* Remove package-lock.json as this repo uses pnpm

* Fix test to check for normalizedUrl after merge and fix linting issues

* Add explanatory comment for $fetch.raw usage and remove test file

Co-authored-by: serhalp <[email protected]>

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: serhalp <[email protected]>
Co-authored-by: Philippe Serhal <[email protected]>

Author: Copilot

server/api/inspect-url.post.ts

@@ -31,11 +31,13 @@ export default defineEventHandler(async (event) => {
   }
 
   const startTime = Date.now()
-  // TODO(serhalp) `$fetch` automatically throws on 4xx, but we'd like to treat those as valid.
+  // Use $fetch.raw to get both response status and headers, and ignoreResponseError
+  // to prevent automatic error throwing on 4xx/5xx responses (we want to inspect those too)
   const { status, headers } = await $fetch.raw(normalizedUrl, {
     headers: {
       'x-nf-debug-logging': '1',
     },
+    ignoreResponseError: true,
   })
   const durationInMs = Date.now() - startTime