Traffic Server requires either (1) a remap rule or (2) disabling remap_required
in records.config. This is not specific to the intercept plugin. If you don't
want (2) you can always add an identity remap to remap.config and map the URL
to itself.
Github user jrushf1239k commented on the pull request:
https://github.com/apache/trafficserver/pull/424#issuecomment-196387624
Updated the README and added source code comments on the requirement that
signing query parameters must always be appended to the end of any application
query
Github user jacksontj commented on the pull request:
https://github.com/apache/trafficserver/pull/523#issuecomment-196392204
Created new Jira, https://issues.apache.org/jira/browse/TS-4272. @zwoop
since this is such a simple patch I assume we'll want to backport this? If so,
which ver
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/523
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user ryandurfey opened a pull request:
https://github.com/apache/trafficserver/pull/524
Update header_rewrite.en.rst to add example of applying cache control
headers
Added an example of applying cache control headers at the CDN based on
origin path.
You can merge this pull
Hello John,
Thanks for your suggestion.
In fact, the request was malformed or it was not recognized.
I'm now using curl to ask for a byte-range, and it worked.
But even after multiple requests for the same asset, ATS will not cache it.
I was expecting that with this plugin in place (cache_range_r
Hello Nuno,
I see from the logs you sent that your origin does not support range
requests so this plugin, cache_range_requests, will be of little use to
you.
You might want to have a look at the background_fetch plugin. It¹s
documented here,
https://trafficserver.readthedocs.org/en/6.0.x/refere
Hi Alan,
I tried to add a remap rule like this:
regex_map http://(.*)/(.*) http://$1/$2
I still get the following error:
20160314.19h04m03s RESPONSE: sent 127.0.0.1 status 404 (Not Found on
Accelerator) for 'http://.'
So I tried your suggestion #2 and set the remap_required to 0 (didn't wan
is there another way where the TS (or plugin in TS) can act as a server?
thx.
On Mon, Mar 14, 2016 at 12:15 PM, Dk Jack wrote:
> Hi Alan,
> I tried to add a remap rule like this:
>
> regex_map http://(.*)/(.*) http://$1/$2
>
> I still get the following error:
>
> 20160314.19h04m03s RESPONSE: sen
I wouldn't bother with that complex of a remap rule - just turn off remap
required entirely.
http://trafficserver.readthedocs.org/en/6.0.x/reference/configuration/records.config.en.html#proxy-config-url-remap-remap-required
If that doesn't work you'll need to turn on debug tags "http|remap" to se
Hello John
I'm testing now the background_fetch plugin with byte-range requests.
It seems that for new requests (content not in cache), ATS will never cache
that content, even after several requests (byte-range requests).
Also, ATS is delivering the whole content with HTTP 200 status code.
But
Github user zwoop commented on the pull request:
https://github.com/apache/trafficserver/pull/504#issuecomment-196630409
This looks clean to me, +1. I assume it's been tested both in the old
behavior, and the new behavior, right ?
---
If your project is set up for it, you can reply t
12 matches
Mail list logo
