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

SDK reports a status 200 instead of a 304

Open
#1,008 9 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
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, kotlin

Research direction

No source file or test is named. Reproduce an Android request with server-side ETags using SDK 1.11.1 and OkHttp 4.9.0, then trace how the RUM session resource records the response status; done when a 304 request is reported as 304 rather than 200.

Written by the indexing model from the issue text.

Description

enhancement

Thanks for taking the time for reporting an issue!

Describe what happened
My Android app launched a call that returned a 304, and datadog RUM session resource says it has a 200 status instead of a 304.

Steps to reproduce the issue:
Have e-tags server side

Describe what you expected:
Hi guys! I hope you're doing fine! I was recently investigating something in my project, and I found out datadog is not reporting 304 status on some requests. You have an example here

x-datadog-origin: rum
x-datadog-parent-id: 6329686970868304213
x-datadog-sampling-priority: 1
x-datadog-trace-id: 8589955483293502493

(I have the AS screenshot of the request, but I can't share it publicly, give me an email, and I'll get back to you)

I've also asked my teammates on iOS to look at it because I think they might have the same problem.

Have a great day.

Additional context

  • Android OS version: Any
  • Device Model: Any
  • Datadog SDK version: 1.11.1
  • Versions of any other relevant dependencies (OkHttp, …): okHttpVersion (4.9.0)
  • Proguard configuration: Can't disclose
  • Gradle Plugins: Can't disclose
Dominant language
Kotlin
Stars
227
Forks
86
Avg merge
1d 15h
Merged PRs (30d)
76

Getting set up

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 DataDog/dd-sdk-android

All issues in DataDog/dd-sdk-android

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.