Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Tracker: request plumbing — proxy, initial-load failures, and headers

Open
  • Is something wrong?
#290 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
api, backend

Research direction

This is an umbrella tracker that explicitly introduces no new scope and closes nothing itself — pick one sub-issue instead: #282 (proxy forwarding content-encoding after decompression), #125/#126 (initial-load requests firing before state is ready, fixed together), #280 (site-wide Referrer-Policy header), or #281 (a decision on the dormant permalink feature). Read the sub-issue for the concrete file and failing request; 'done' means that sub-issue's own fix lands and closes it.

Written by the indexing model from the issue text.

Description

bug tracker

Summary

Everything here is the app's own request layer: what the proxy forwards, what fires before state is ready, and what headers go out. Several are visible in the same browser console on the same page load.

Why these are grouped

#125 and #126 are the same shape of bug. Both fire a malformed request during initial page load, before the relevant state exists: #125 POSTs a hardcoded default SAT3 instance that production no longer accepts, #126 POSTs a gadget-map request with an empty reduction= param. Both return 400, both appear in the same console on the same load, and both are a "don't fire until state is ready" guard.

#282 is the more severe one — the proxy forwards the upstream content-encoding header after already decompressing the body, so the browser tries to decompress twice and fails. That breaks every response large enough to be compressed, which is most real data against production.

#280 (site-wide Referrer-Policy) is a header change in the same proxy/server config #282 touches. #281 (decide the fate of the dormant permalink/share feature, whose read-back path is switched off) is the same request/state plumbing and is a decision rather than an implementation.

Note #125 is really answered by ReduxISU/Redux#218 — once the backend advertises instanceFormat, the frontend has a correct default to use instead of a hardcoded one.

Suggested order

  1. #282 — stop forwarding content-encoding (unblocks batch endpoints against production)
  2. #125 + #126 — guard both initial-load requests, together
  3. #280 — Referrer-Policy in the same config
  4. #281 — decide: finish the permalink feature or remove it

Sub-issues

Tracked as sub-issues below. None of them are closed by this issue — each closes as its own work lands.

Related (not re-parented)

Opened by other contributors, so linked for context only — their state is unchanged:

  • #125 — [Bug]: Default SAT3 instance uses stale format — 400 on problemInstance at load (@wrigjl)
  • #126 — [Bug]: gadgets request fires with empty reduction on initial load (400) (@wrigjl)

Issue Handling

Umbrella/tracker issue grouping existing work; no new scope is introduced here. Nothing is closed by this issue directly.

Dominant language
JavaScript
Stars
3
Forks
18
Avg merge
1d 3h
Merged PRs (30d)
35

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ReduxISU/Redux_GUI

All issues in ReduxISU/Redux_GUI

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.