[jira] [Assigned] (TS-2315) ESI Plugin: fetcher does not handle error gracefully

[ https://issues.apache.org/jira/browse/TS-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2315: - Assignee: Leif Hedstrom > ESI Plugin: fetcher does not handle error gracefully > ---

[jira] [Updated] (TS-2315) ESI Plugin: fetcher does not handle error gracefully

[ https://issues.apache.org/jira/browse/TS-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2315: -- Fix Version/s: 4.1.0 > ESI Plugin: fetcher does not handle error gracefully >

[jira] [Commented] (TS-2316) Merging LinkedIn's header_rewrite improvements upstream

[ https://issues.apache.org/jira/browse/TS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811864#comment-13811864 ] Leif Hedstrom commented on TS-2316: --- Looking forward to the pull request, I'll shepherd it.

[jira] [Assigned] (TS-2316) Merging LinkedIn's header_rewrite improvements upstream

[ https://issues.apache.org/jira/browse/TS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2316: - Assignee: Leif Hedstrom > Merging LinkedIn's header_rewrite improvements upstream >

[jira] [Updated] (TS-2316) Merging LinkedIn's header_rewrite improvements upstream

[ https://issues.apache.org/jira/browse/TS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2316: -- Fix Version/s: 4.2.0 > Merging LinkedIn's header_rewrite improvements upstream > -

[jira] [Updated] (TS-2316) Merging LinkedIn's header_rewrite improvements upstream

[ https://issues.apache.org/jira/browse/TS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ivanov updated TS-2316: -- Description: At LinkedIn we have following improvements to header_rewrite module: * Variable expansion for

[jira] [Commented] (TS-886) Grace mode supported, very useful for slow origins

[ https://issues.apache.org/jira/browse/TS-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811721#comment-13811721 ] Chan, Ricky commented on TS-886: I am in annual leave and won't be back till 4th November. In

[jira] [Created] (TS-2316) Merging LinkedIn's header_rewrite improvements upstream

Alexey Ivanov created TS-2316: - Summary: Merging LinkedIn's header_rewrite improvements upstream Key: TS-2316 URL: https://issues.apache.org/jira/browse/TS-2316 Project: Traffic Server Issue Type

[jira] [Resolved] (TS-886) Grace mode supported, very useful for slow origins

[ https://issues.apache.org/jira/browse/TS-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach resolved TS-886. Resolution: Done Consensus on IRC is that the RFC 5861 plugin is the way to do this. If it doesn't address all

[jira] [Commented] (TS-886) Grace mode supported, very useful for slow origins

[ https://issues.apache.org/jira/browse/TS-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811719#comment-13811719 ] James Peach commented on TS-886: The RFC 5861 plugin is the recommended way to do this. > Gra

[jira] [Updated] (TS-2315) ESI Plugin: fetcher does not handle error gracefully

[ https://issues.apache.org/jira/browse/TS-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan updated TS-2315: - Attachment: 2315_patch.diff > ESI Plugin: fetcher does not handle error gracefully > ---

[jira] [Created] (TS-2315) ESI Plugin: fetcher does not handle error gracefully

Kit Chan created TS-2315: Summary: ESI Plugin: fetcher does not handle error gracefully Key: TS-2315 URL: https://issues.apache.org/jira/browse/TS-2315 Project: Traffic Server Issue Type: Bug

[jira] [Commented] (TS-2302) log collation causes error logging to stop

[ https://issues.apache.org/jira/browse/TS-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811509#comment-13811509 ] Yunkai Zhang commented on TS-2302: -- Ok. > log collation causes error logging to stop >

[jira] [Updated] (TS-2310) document the map_with_recv_port remap rule type

[ https://issues.apache.org/jira/browse/TS-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach updated TS-2310: Assignee: Manjesh Nilange [~manjeshnilange] can you take a crack at this? > document the map_with_recv_port r

[jira] [Commented] (TS-1666) Plugins, clustering and core crashes when share_server_sessions=2

[ https://issues.apache.org/jira/browse/TS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811357#comment-13811357 ] William Bardwell commented on TS-1666: -- I am not using any weird threads and proxy.confi

[jira] [Commented] (TS-1955) read_while_writer sends wrong response for range request.

[ https://issues.apache.org/jira/browse/TS-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811289#comment-13811289 ] Leif Hedstrom commented on TS-1955: --- [~genext] Btw, the setting is most certain overridable

[jira] [Commented] (TS-1955) read_while_writer sends wrong response for range request.

[ https://issues.apache.org/jira/browse/TS-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811286#comment-13811286 ] Leif Hedstrom commented on TS-1955: --- I cloned this into TS-2314, which is to add a new feat

[jira] [Updated] (TS-2314) New config to allow unsatifiable Range: request to go straight to Origin

[ https://issues.apache.org/jira/browse/TS-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2314: -- Fix Version/s: (was: 4.1.0) 4.2.0 > New config to allow unsatifiable Range: request

[jira] [Updated] (TS-2314) New config to allow unsatifiable Range: request to go straight to Origin

[ https://issues.apache.org/jira/browse/TS-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2314: -- Assignee: (was: Leif Hedstrom) > New config to allow unsatifiable Range: request to go straight to Ori

[jira] [Commented] (TS-2314) New config to allow unsatifiable Range: request to go straight to Origin

[ https://issues.apache.org/jira/browse/TS-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811285#comment-13811285 ] Leif Hedstrom commented on TS-2314: --- Cloned this for a new feature; This would allow a conf

[jira] [Created] (TS-2314) New config to allow unsatifiable Range: request to go straight to Origin

Leif Hedstrom created TS-2314: - Summary: New config to allow unsatifiable Range: request to go straight to Origin Key: TS-2314 URL: https://issues.apache.org/jira/browse/TS-2314 Project: Traffic Server

[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type

[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Description: Currently, remap rules are stored in different structures and looked up separately based on type (

[jira] [Resolved] (TS-2313) redirect with map

[ https://issues.apache.org/jira/browse/TS-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-2313. --- Resolution: Duplicate > redirect with map > - > > Key: TS-2313 >

[jira] [Created] (TS-2313) redirect with map

Andrey Petrov created TS-2313: - Summary: redirect with map Key: TS-2313 URL: https://issues.apache.org/jira/browse/TS-2313 Project: Traffic Server Issue Type: Bug Components: Core