Case study: reconstructing custom request-header signatures on a government procurement site

·2 views

A DEV Community write-up, part of a 30-case JavaScript reverse-engineering series, walks through how the author reconstructed custom request headers used by a provincial government procurement e-marketplace. The target endpoint for its announcement list required four non-standard headers, one produced by RSA encryption and another by a nested md5(sha1(...)) hash. The author located the header-generating logic by setting XHR breakpoints and searching for encryption-related identifiers in obfuscated JavaScript. The article presents the approach as an educational explanation of the technique, with real domains and site-specific constants replaced by placeholders.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why the First Two Weeks of an AI Deployment Decide Its Outcome

An engineer embedded with a customer during the opening stretch of a deployment works to replace assumptions with facts before building anything. The brief written in a meeting room often describes a proxy rather than the real problem, which becomes clear only after observing daily operations. The article outlines five principles: focus on the actual problem rather than a stated tool, request data and system access immediately, examine raw unfiltered data before designing, select a small but meaningful first workflow, and identify every stakeholder who could block the work. Skipping this phase, it argues, results in building the wrong solution efficiently. Early discovery turns potential delays into useful signals about how the deployment will run.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Semurg answers 4-hop query on 1.8-billion-edge graph in 1.41 s; Neo4j and FalkorDB fail to finish

A benchmark used SNAP's com-Friendster graph, with 65.6 million people and 1.8 billion relationships, under a 12 GB memory limit for every engine. Semurg answered a 4-hop query about one person's network in a median of 1.41 seconds. Neo4j loaded the graph but had not answered that query when its 2,345-second time budget ran out. FalkorDB exhausted its 12 GB memory while loading and never reached a query. Semurg also completed walks from two hops up to 131,072 hops, with run times levelling off at about 6.7 seconds beyond 16 hops because the graph is small-world. ArcadeDB, ArangoDB and SurrealDB were not fairly measured or have no result in this run and are slated for the next one.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Agent Web Access lets AI agents read rendered web pages as markdown for $0.001 per call

LLM agents often fail to read real web pages with a plain HTTP request, which returns empty shells, cookie walls, or bulky markup. Agent Web Access offers a pay-per-call service that renders pages in a real browser, strips navigation and ads, and returns clean markdown. It requires no account or API key, and each call is paid in USDC on Base via the open x402 protocol. Endpoints cover fetching markdown or text, extracting CSS-selector elements, and generating screenshots or PDFs, priced between $0.001 and $0.005. The author reports running the fetch example against the Hacker News front page, which returned status 200 and about 11 KB of markdown for $0.001.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Microagi Launches Project Aimed at Accelerating Embodied AGI Development

Microagi has published a website describing its work on accelerating embodied artificial general intelligence. The item surfaced on Hacker News, where it gathered a few points and no discussion comments at the time of posting. The source material provides only the project name, a link to the company's site, and basic community engagement metrics. Specific technical details, timelines, funding, or research results are not included in the available text.

0 comments Read more at Hacker News