Skip to content

Conversation

@jpeach
Copy link
Contributor

@jpeach jpeach commented Aug 22, 2016

No description provided.

@atsci
Copy link

atsci commented Aug 22, 2016

FreeBSD build failed! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/584/ for details.

@atsci
Copy link

atsci commented Aug 23, 2016

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/480/ for details.

@atsci
Copy link

atsci commented Aug 23, 2016

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/586/ for details.

@atsci
Copy link

atsci commented Aug 23, 2016

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/481/ for details.

@zwoop zwoop added the Plugins label Aug 23, 2016
@zwoop zwoop added this to the 7.0.0 milestone Aug 23, 2016
@zwoop zwoop self-assigned this Aug 23, 2016
@zwoop
Copy link
Contributor

zwoop commented Aug 23, 2016

I guess I don't have a strong opinion, but it seems unfortunate to me to introduce these new options as headers, rather than URI components. The original plugin for lighthttpd did everything in the URI paths, no? Keeping it that way seems more consistent, and easier to use for e.g. setting up various performance and load patters where you want to mix various options for various requests.

In a sense, it'd cool to mimic some of the behavior of httpbin.

@bryancall
Copy link
Contributor

Instead of headers I would like to seem them in the URL. Possibly as query parameters.

@jpeach
Copy link
Contributor Author

jpeach commented Aug 23, 2016

It is done in headers so that you can trivially hit the same URL with different attributes. For example, hit URL1 with a short MaxAge to populate the cache. Then hit URL1 again with a long delay to lock the cache entry, then hit URL1. This is much harder to do with query parameters, though I have no objection to adding them as an additional mechanism.

@jpeach
Copy link
Contributor Author

jpeach commented Aug 23, 2016

Are we good with headers (at least for now)?

@zwoop
Copy link
Contributor

zwoop commented Aug 24, 2016

I dislike the inconsistency, but your explanation / use case makes a lot of sense. And if we agree that this makes things better, and not worse, do it. Maybe file a Jira to have a future addition to support both headers and URIs for all parameters?

@jpeach jpeach merged commit 70f8876 into apache:master Aug 24, 2016
bneradt added a commit to bneradt/trafficserver that referenced this pull request Feb 6, 2024
I got a review comment asking me to handle the Content-Length size in
the plugin rather than in the HttpSM. This change pulls that in here to
keep our internal release in parity with ASF.
masaori335 pushed a commit to masaori335/trafficserver that referenced this pull request May 29, 2025
* header_rewrite: Don't check URLs in request lines

* header_rewrite: Don't check URLs in request lines

* ip_allow: Skip all existing tests for UDS and add a new test that uses PP

* Fix indentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants