mdn / mdn/mdn-http-observatory
Observatory returns a `502` error when scanning `www.bloomberg.com`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 141
- Forks
- 34
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 14
Description
What information was incorrect, unhelpful, or incomplete?
We are using the Observatory as a tool to improve our site security at www.bloomberg.com.
What did you expect to see?
I expected the scan for our site www.bloomberg.com to either work, or at least give us an 500 error through the v2 /scan API that told us what error code the scanner is seeing from our site.
Instead, we are seeing a 502 error returned from both the API and the Observatory site (via the network tab):
<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>502 Server Error</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Server Error</h1>
<h2>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds.</h2>
<h2></h2>
</body></html>
So we have no way of knowing whether this issue is on our side or on the hosted scanner side.
I would like to note that running this from a local computer (via npx or otherwise), targeting the same www.bloomberg.com domain did work. But we would like to have our public scores accurately updated on this site, if possible.
Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the v2 /scan API entry point and compare its hosted behavior with a local npx scan against www.bloomberg.com. The issue is resolved when the hosted scan completes or returns an informative scanner error instead of a generic 502 response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100