trafficserver icon indicating copy to clipboard operation
trafficserver copied to clipboard

Apache Traffic Server™ is a fast, scalable and extensible HTTP/1.1 and HTTP/2 compliant caching proxy server.

Results 518 trafficserver issues
Sort by recently updated
recently updated
newest added

We run a proxy server in front of ATS and noticed this problem when the number of streams on a connections gets close to the maximum, and some streams are...

HTTP/2
Bug
Stale

The test fails because the via numbers differ from the gold file. I don't understand the cache very deeply, so hopefully someone more skilled in that area could take a...

AuTest
Ubuntu

My use case is almost solved by the `access_control` plugin, but instead of having a JWT created by an Application/Origin, I have a client JWT assertion that contains e.g. `sub`....

Stale

These are both obsoleted, and confusing to have around: ``` RecInt REC_readInteger(const char *name, bool *found, bool lock = true); RecFloat REC_readFloat(char *name, bool *found, bool lock = true); RecCounter...

Core
Cleanup
Good First Issue

Add active (and finished) issues / tasks here. - [ ] Stuff + link - [ ] Lots of little stuff - [ ] More options for enabling / disabling...

Cleanup

This turned out to be a little more complicated than expected, because these records.config are actually used as part of the mechanisms for reloading configuration files. But we should get...

Configuration
Cleanup
Proposal
Umbrella
Stale

handle_cache_operation_on_forward_server_response sets RANGE_NOT_TRANSFORM_REQUESTED even if the server returns a response that doesn't match with the cached response. This causes ATS to send incorrect client responses. For example, while revalidating the...

ATS log support for quic information - First document which fields are supported (we might need to break up this issue into multiple issues) Types of fields to log: -...

Logging
QUIC
Good First Issue
HTTP/3
Stale

In the s3_auth plugin for v4 signatures, there is an undocumented feature that allows for an expiration configuration. The plugin goes through considerable effort to reload a nearly expired token...

I see it created, but nothing updates it. Is that a bug, or should we just remove this?

Metrics