fix: handle unparseable mime-type

[diogoosorio]

📜 Description

Caught this one in production in one of our apps

Which we could easily replicate by sending a request with a Content-Type: invalid (which is indeed an invalid mime-type). The app returns a 500 error.

💡 Motivation and Context

This shouldn't cause an exception on the filter, determining if the content-type of the body is an acceptable one should not be handled by the Sentry request filter.

• resolves: SentrySpringFilter throws InvalidMimeTypeException with an invalid content-type header #4938

💚 How did you test it?

Create a minimal app Spring Boot MVC app with a sentry.max-request-body-size property defined. Include sentry-spring-boot-starter-jakarta and send a request:

curl -X POST --header "Content-Type: invalid" --location "http://localhost:8080/demo" --data "{}"

See that a 500 error is returned. Re-run with this change and see that the request now goes through the remainder of the filter pipeline.

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

[sentry]

Bug: The sentry-spring-jakarta module's shouldCacheMimeType() method lacks InvalidMimeTypeException handling for invalid Content-Type headers.
_{Severity: CRITICAL | Confidence: High}

🔍 Detailed Analysis

The sentry-spring-jakarta module's shouldCacheMimeType() method in sentry-spring-jakarta/src/main/java/io/sentry/spring/jakarta/SentrySpringFilter.java lacks proper exception handling. When applications using this module with sentry.max-request-body-size defined receive requests with invalid Content-Type headers (e.g., Content-Type: invalid), MimeType.valueOf(contentType) throws an InvalidMimeTypeException. This unhandled exception causes the application to crash with a 500 error, preventing the request from proceeding through the filter pipeline.

💡 Suggested Fix

Wrap the shouldCacheMimeType() method in sentry-spring-jakarta/src/main/java/io/sentry/spring/jakarta/SentrySpringFilter.java with a try-catch block for InvalidMimeTypeException, matching the fix applied to other modules.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: sentry-spring/src/main/java/io/sentry/spring/SentrySpringFilter.java#L132-L143

Potential issue: The `sentry-spring-jakarta` module's `shouldCacheMimeType()` method in
`sentry-spring-jakarta/src/main/java/io/sentry/spring/jakarta/SentrySpringFilter.java`
lacks proper exception handling. When applications using this module with
`sentry.max-request-body-size` defined receive requests with invalid `Content-Type`
headers (e.g., `Content-Type: invalid`), `MimeType.valueOf(contentType)` throws an
`InvalidMimeTypeException`. This unhandled exception causes the application to crash
with a 500 error, preventing the request from proceeding through the filter pipeline.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 4294118}