Skip to content

Navigation Menu

Appearance settings

View all features
- BY COMPANY SIZE
  Enterprises
  Small and medium teams
  Startups
  Nonprofits
- BY USE CASE
  App Modernization
  DevSecOps
  DevOps
  CI/CD
  View all use cases
- BY INDUSTRY
  Healthcare
  Financial services
  Manufacturing
  Government
  View all industries
View all solutions
- EXPLORE BY TOPIC
  AI
  Software Development
  DevOps
  Security
  View all topics
- EXPLORE BY TYPE
  Customer stories
  Events & webinars
  Ebooks & reports
  Business insights
  GitHub Skills
- SUPPORT & SERVICES
  Documentation
  Customer support
  Community forum
  Trust center
  Partners
View all resources
- COMMUNITY
  GitHub SponsorsFund open source developers
- PROGRAMS
  Security Lab
  Maintainer Community
  Accelerator
  GitHub Stars
  Archive Program
- REPOSITORIES
  Topics
  Trending
  Collections
- ENTERPRISE SOLUTIONS
  Enterprise platformAI-powered developer platform
- AVAILABLE ADD-ONS
  GitHub Advanced SecurityEnterprise-grade security features
  Copilot for BusinessEnterprise-grade AI features
  Premium SupportEnterprise-grade 24/7 support
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Appearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

CenterForDigitalHumanities / rerum_server_nodejs Public

Notifications You must be signed in to change notification settings
Fork 4
Star 3

Code
Issues 65
Pull requests 7
Actions
Projects
Models
Security and quality
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Models
Security and quality
Insights

Handle Bad `Content-Type` Headers RESTfully#255

Merged

thehabes merged 43 commits intomainCenterForDigitalHumanities/rerum_server_nodejs:mainfrom

246-bad-content-type-headersCenterForDigitalHumanities/rerum_server_nodejs:246-bad-content-type-headersCopy head branch name to clipboard

Mar 25, 2026

Conversation Commits43 (43)Checks Files changed

Merged

Handle Bad `Content-Type` Headers RESTfully#255
thehabes merged 43 commits intomainfrom
246-bad-content-type-headers

Commits

Commits on Mar 23, 2026

First pass at handling bad Content-Type headers. Focus on a way to do it that doesn't have to touch man files in the api/ directory.
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing
thehabes
committed
Changes while reviewing and testing
thehabes
committed
Changes while reviewing and testing
thehabes
committed

Commits on Mar 24, 2026

Fix createExpressError
thehabes
committed
Fix createExpressError
thehabes
committed
Changes while testing and reviewing
thehabes
committed
Changes while testing and reviewing
thehabes
committed
Changes while reviewing and testing
thehabes
committed
Changes while reviewing and testing
thehabes
committed
Changes while reviewing and testing
thehabes
committed
Changes while reviewing and testing
thehabes
committed
reject content-type headers that have multiple or duplicate types
thehabes
committed
ah ok get those generic mongo error codes
thehabes
committed
ah nebermind
thehabes
committed
refactor how Content-Type headers are checked
thehabes
committed
refactor how Content-Type headers are checked
thehabes
committed
refactor how Content-Type headers are checked
thehabes
committed
refactor how createExpressError is used
thehabes
committed
changes while testing and reviewing
thehabes
committed
It is about time we clean these old logs out. They are not useful because the endpoint is logged.
thehabes
committed
Don't respond with the full token
thehabes
committed
rename
thehabes
committed
Changes while testing and reviewing
thehabes
committed
I like the way it errors this way better
thehabes
committed
Update for tests
thehabes
committed
yikes bad not === check
thehabes
committed
catch comma and semicolon smugglers
thehabes
committed

Commits on Mar 25, 2026

there is a valid version of the header with a comma. Make sure 415 doesn't occur for a valid header.
thehabes
committed
changes while testing
thehabes
committed
changes while testing
thehabes
committed
changes while testing
thehabes
committed

Footer

© 2026 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Community
Docs
Contact

You can’t perform that action at this time.