Urgent.News

What's breaking now, across thousands of outlets.

Tech

Marketplace Webhook Signature Check After Deploy With Raw Body Admission Controls

The page a marketplace team should rehearse is painfully specific: a webhook signature check starts failing after a deploy, platform events stop entering the backend, and the on-call must decide how much refused traffic the recovery budget can tolerate. Keep the admission path small. Capture the original request bytes before JSON middleware, verify those bytes, and parse only after verification…

When a webhook signature check fails after an Express deploy, the problem often lies in middleware consuming the raw body before the handler runs. To resolve this, preserve the raw request bytes before JSON middleware processes them, and verify those bytes before parsing. Re-serializing the parsed object after verification can alter the signed representation, so it's crucial to keep the original bytes intact.

Always check the registered signing secret, as rotation can produce similar symptoms. Reject verification failures with a status that the sender treats as non-retryable, and log the error with the registration ID. This drill aims to separate refusal of legitimate events from downstream processing failures, allowing operators to identify the root cause and avoid inflating the acceptance count.

Verification should occur after capturing the original request bytes, and the ordering of steps is critical. For testing, a Go sender can simulate events without modifying the production runtime. Before implementing changes, compare the active signing secret with the receiver's configuration to account for rotated secrets. Log verification failures with the registration ID attached to aid troubleshooting, but avoid sharing sensitive marketplace content in routine error reports.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Extract the audio from a video with ffmpeg from command line

You have a recording of a call or a talk, and you only want the audio. How do you do it? You ask an AI, and it gives you the classic line: ffmpeg -i "Team call.mp4" -vn -acodec copy out.mp3 It fails…

  • Use ffmpeg command-line tool to extract audio from video
  • Script queries ffprobe for audio stream, selects output format
  • Handles errors, outputs audio file with same name, different extension

OpenHands vs SWE-Agent vs AutoGen: Best Autonomous Dev Tool for Real T

Updated June 3, 2026. Current GitHub stars, licenses, official product pages, and community reports were checked before writing this expanded comparison.

  • OpenHands excels in end-to-end cloud coding with Docker sandbox
  • SWE-agent specializes in GitHub issue-to-patch automation
  • AutoGen offers most flexible framework for multi-agent orchestration

Building a Canada-wide licensed cannabis store dataset from official provincial registries

By Where's The Weed At Canada has no single national list of licensed cannabis retailers. Retail is a provincial and territorial matter, so there are 13 registries, each with its own format, update…

  • Canada lacks a national cannabis store list, relying on 13 provincial registries.
  • The compiled dataset contains 4,030 licensed, open cannabis stores nationwide.
  • The full dataset and methodology are available at wherestheweedat.ca/stats.

More from Saturday 21 November →