Skip to main content

Exercise 06 submission

Name: Date: App used: repository student folder / instructor kit

Prediction​

What should an ordinary visitor receive when the service fails?

Observations​

RequestBefore: status and important fieldsAfter: status and important fields
Working status
Simulated failure

Two unnecessary diagnostic details and why analogous real details matter:

Response evidence​

For each section, paste the request line, HTTP status and complete JSON from your run, or attach a readable screenshot containing all three. Save each response before clicking the next button.

Before repair: working status​

[Paste your evidence here.]

Before repair: simulated failure​

[Paste your evidence here.]

After repair: working status​

[Paste your evidence here.]

After repair: simulated failure​

[Paste your evidence here.]

Repair evidence​

Original setting: Repaired setting: How I saved, stopped and restarted the app:

Verification​

Paste the full output of node checks.mjs:

Explanation​

  1. Why this is configuration risk rather than a dependency vulnerability:
  2. Why HTTP503 and SERVICE_UNAVAILABLE should remain:
  3. Why hiding diagnostics in the browser alone is insufficient:
  4. One reason this change alone does not establish production security:

Reflection​

One thing I would ask a developer to review before deploying a real application:

Screenshot preview