[jira] [Commented] (TS-2913) "Could not process this request" error when using redirect remap
[ https://issues.apache.org/jira/browse/TS-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053165#comment-14053165 ] Leif Hedstrom commented on TS-2913: --- [~ask] I think Ethan is correct. We need to verify against v5.0.0 though. > "Could not process this request" error when using redirect remap > > > Key: TS-2913 > URL: https://issues.apache.org/jira/browse/TS-2913 > Project: Traffic Server > Issue Type: Bug > Components: Remap API >Reporter: Ask Bjørn Hansen >Assignee: Leif Hedstrom > Fix For: 5.1.0 > > > With this remap rule: > redirect http://foo.example.com/ \ > http://foo.example.com/path > The server responds with a Location: header as expected, but also with an > error template. (This is on 4.2.1-ish). > > > Error > > > Error > > > Description: Could not process this request. > > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2643) Origin Server Throttling
[ https://issues.apache.org/jira/browse/TS-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053183#comment-14053183 ] Leif Hedstrom commented on TS-2643: --- You can do this on the network layer. Use the available linux tools to throttle the bandwidth allowed. Just do some googling. > Origin Server Throttling > - > > Key: TS-2643 > URL: https://issues.apache.org/jira/browse/TS-2643 > Project: Traffic Server > Issue Type: New Feature > Components: Network, Plugins >Reporter: Faysal Banna > Fix For: sometime > > > Hi Guys > wonder if its too much work to request for implementing a feature to rate > limiting (throttling) bandwidth (bytes/sec) for data from Origin Servers , > yet i know not where would it be implemented, and since we take most of the > headers requested and responses in the header_rewrite and we can > apply/override rules per txn in header_rewrite, The idea is that since we do > time condition and set background filling and chance some stuff in the > header_rewrite > why cann't we issue a configurable request to records.config to limit this > txn. > its for the reason needed so that at some peak hours clients who are using > downloads or watching some porn movies would be rate limited at those times, > and maybe for example windows updates that work in background would not > consume much of my bandwidth from origin server > and leave space more for the interactive pages and stuff to pass through > thats why i said if it possible to do it in header_rewrite plugin cause as > far its the only plugin i seen that can override configurable rules as per > request > am not sure how the internals of the ATS works per transaction. thats why my > thought was in header_rewrite. yet i guess it might land in some new plugin > throttle_plugin or so. taking into consideration that it needs to inspect the > requested headers and the time it is requested at. > much regards > Faysal Banna -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2916) combo_handler does not set the response headers properly
[ https://issues.apache.org/jira/browse/TS-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2916: -- Assignee: Kit Chan > combo_handler does not set the response headers properly > > > Key: TS-2916 > URL: https://issues.apache.org/jira/browse/TS-2916 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Feifei Cai >Assignee: Kit Chan > Labels: review, yahoo > Fix For: 5.1.0 > > Attachments: TS-2916.diff > > > # "Cache-Control: max-age=xxx" > combo_handler plugin should parse each url's max-age value in "Cache-Control" > header, and use the minimal value in the response header. The hard-code "10 > years" max-age prevents cache from refresh, even though we have parsed the > value in "Expires" headers. > See > [rfc2616-sec14.9.3|http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.3]: > "If a response includes both an Expires header and a max-age directive, the > max-age directive overrides the Expires header, even if the Expires header is > more restrictive." > # Duplicated headers > We add support for whitelist of headers in a recent > [commit|https://github.com/apache/trafficserver/commit/f61b1b416f4bb99854c6b6c77b12f742b5af9ca8] > When we have added headers specified in whitelist, we need to check for > duplicated headers in the following response write actions. > # Multiple values > Some headers has multiple values, e.g. "Cache-Control: max-age=3600, public". > It has 2 values: "max-age=3600" and "public". > We need to parse all the values for each header specified in whitelist. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2899) traffic server does not build on ppc64 little endian
[ https://issues.apache.org/jira/browse/TS-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053189#comment-14053189 ] Leif Hedstrom commented on TS-2899: --- Hmmm, considering we only support little endian, I don't think this is an "endian" issue. Rather, we don't support PPC. I don't know that there ever will be support for PPC, unless someone chimes that they care about PPC, we should close this as won't fix. > traffic server does not build on ppc64 little endian > > > Key: TS-2899 > URL: https://issues.apache.org/jira/browse/TS-2899 > Project: Traffic Server > Issue Type: Wish > Components: Build >Reporter: Breno Leitao > > When trying to build traffic search on ppc64 little endian, I got the > following error: > c++ -DHAVE_CONFIG_H -I. -I../../lib/ts -I../../lib -I../../lib/records > -I../../lib/ts -D_FORTIFY_SOURCE=2 -Dlinux -D_LARGEFILE64_SOURCE=1 > -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -I/usr/include/tcl8.5 > -I/usr/include/libxml2 -Wunused-parameter -g -O2 -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++11 -pipe > -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing > -Wno-invalid-offsetof -MT EventSystem.o -MD -MP -MF .deps/EventSystem.Tpo -c > -o EventSystem.o EventSystem.cc > In file included from ../../lib/ts/libts.h:64:0, > from P_EventSystem.h:34, > from EventSystem.cc:31: > ../../lib/ts/ink_queue.h:144:2: error: #error "unsupported processor" > #error "unsupported processor" > If someone want to port it to ppc64 little endian, you can find a machine > available at https://wiki.debian.org/ppc64el#Development_machines > Thank you, > Breno -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2915) SEGV occurs when POST request was posted without Expect: 100-continue header
[ https://issues.apache.org/jira/browse/TS-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2915: -- Fix Version/s: 5.1.0 > SEGV occurs when POST request was posted without Expect: 100-continue header > > > Key: TS-2915 > URL: https://issues.apache.org/jira/browse/TS-2915 > Project: Traffic Server > Issue Type: Bug > Components: HTTP >Reporter: Ryo Okubo > Fix For: 5.1.0 > > Attachments: bugfix.diff > > > The patch merged on TS-1125 has a bug that occurs Segmentation fault. > It's reproduced when send_100_continue_response option was enabled and POST > request was posted without Expect: 100-continue header. > Please check follow links. > https://github.com/apache/trafficserver/blob/master/proxy/http/HttpSM.cc#L1898 > https://github.com/apache/trafficserver/blob/master/proxy/http/HttpSM.cc#L3290 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2916) combo_handler does not set the response headers properly
[ https://issues.apache.org/jira/browse/TS-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053190#comment-14053190 ] Leif Hedstrom commented on TS-2916: --- assigning to Kit for review. > combo_handler does not set the response headers properly > > > Key: TS-2916 > URL: https://issues.apache.org/jira/browse/TS-2916 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Feifei Cai >Assignee: Kit Chan > Labels: review, yahoo > Fix For: 5.1.0 > > Attachments: TS-2916.diff > > > # "Cache-Control: max-age=xxx" > combo_handler plugin should parse each url's max-age value in "Cache-Control" > header, and use the minimal value in the response header. The hard-code "10 > years" max-age prevents cache from refresh, even though we have parsed the > value in "Expires" headers. > See > [rfc2616-sec14.9.3|http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.3]: > "If a response includes both an Expires header and a max-age directive, the > max-age directive overrides the Expires header, even if the Expires header is > more restrictive." > # Duplicated headers > We add support for whitelist of headers in a recent > [commit|https://github.com/apache/trafficserver/commit/f61b1b416f4bb99854c6b6c77b12f742b5af9ca8] > When we have added headers specified in whitelist, we need to check for > duplicated headers in the following response write actions. > # Multiple values > Some headers has multiple values, e.g. "Cache-Control: max-age=3600, public". > It has 2 values: "max-age=3600" and "public". > We need to parse all the values for each header specified in whitelist. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2916) combo_handler does not set the response headers properly
[ https://issues.apache.org/jira/browse/TS-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2916: -- Labels: review yahoo (was: yahoo) > combo_handler does not set the response headers properly > > > Key: TS-2916 > URL: https://issues.apache.org/jira/browse/TS-2916 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Feifei Cai > Labels: review, yahoo > Fix For: 5.1.0 > > Attachments: TS-2916.diff > > > # "Cache-Control: max-age=xxx" > combo_handler plugin should parse each url's max-age value in "Cache-Control" > header, and use the minimal value in the response header. The hard-code "10 > years" max-age prevents cache from refresh, even though we have parsed the > value in "Expires" headers. > See > [rfc2616-sec14.9.3|http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.3]: > "If a response includes both an Expires header and a max-age directive, the > max-age directive overrides the Expires header, even if the Expires header is > more restrictive." > # Duplicated headers > We add support for whitelist of headers in a recent > [commit|https://github.com/apache/trafficserver/commit/f61b1b416f4bb99854c6b6c77b12f742b5af9ca8] > When we have added headers specified in whitelist, we need to check for > duplicated headers in the following response write actions. > # Multiple values > Some headers has multiple values, e.g. "Cache-Control: max-age=3600, public". > It has 2 values: "max-age=3600" and "public". > We need to parse all the values for each header specified in whitelist. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2916) combo_handler does not set the response headers properly
[ https://issues.apache.org/jira/browse/TS-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2916: -- Fix Version/s: 5.1.0 > combo_handler does not set the response headers properly > > > Key: TS-2916 > URL: https://issues.apache.org/jira/browse/TS-2916 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Feifei Cai > Labels: review, yahoo > Fix For: 5.1.0 > > Attachments: TS-2916.diff > > > # "Cache-Control: max-age=xxx" > combo_handler plugin should parse each url's max-age value in "Cache-Control" > header, and use the minimal value in the response header. The hard-code "10 > years" max-age prevents cache from refresh, even though we have parsed the > value in "Expires" headers. > See > [rfc2616-sec14.9.3|http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.3]: > "If a response includes both an Expires header and a max-age directive, the > max-age directive overrides the Expires header, even if the Expires header is > more restrictive." > # Duplicated headers > We add support for whitelist of headers in a recent > [commit|https://github.com/apache/trafficserver/commit/f61b1b416f4bb99854c6b6c77b12f742b5af9ca8] > When we have added headers specified in whitelist, we need to check for > duplicated headers in the following response write actions. > # Multiple values > Some headers has multiple values, e.g. "Cache-Control: max-age=3600, public". > It has 2 values: "max-age=3600" and "public". > We need to parse all the values for each header specified in whitelist. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2917) luajit ignores --disable-silent-rules
[
https://issues.apache.org/jira/browse/TS-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053191#comment-14053191
]
Leif Hedstrom commented on TS-2917:
---
Looks like we could maybe do make Q="" on the LuaJIT build?
> luajit ignores --disable-silent-rules
> -
>
> Key: TS-2917
> URL: https://issues.apache.org/jira/browse/TS-2917
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
>Reporter: Arno Toell
>Priority: Minor
>
> When compiling ATS with --disable-silent-rules the luajit tree ignores that
> configure flag. Excerpt:
> {code}
> ./configure --enable-layout=Debian --sysconfdir=/etc/trafficserver
> --libdir=/usr/lib/trafficserver --with-user=root --with-group=root
> --disable-silent-rules --enable-experimental-plugins
> --enable-reclaimable-freelist CFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security"
> CPPFLAGS="-D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security" FCFLAGS="-g -O2
> -fstack-protector --param=ssp-buffer-size=4" FFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4" GCJFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4" LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security"
> OBJCXXFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
> -Werror=format-security" --enable-wccp --enable-linux-native-aio
> ...
> make[3]: Entering directory
> '/home/arno/trafficserver/trafficserver/iocore/eventsystem'
> depbase=`echo EventSystem.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
> c++ -DHAVE_CONFIG_H -I. -I../../lib/ts -I../../lib -I../../lib/records
> -I../../lib/ts -D_FORTIFY_SOURCE=2 -Dlinux -D_LARGEFILE64_SOURCE=1
> -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -I/usr/include/tcl8.6
> -I/usr/include/libxml2 -Wunused-parameter -g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++11 -pipe
> -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing
> -Wno-invalid-offsetof -mcx16 -MT EventSystem.o -MD -MP -MF $depbase.Tpo -c -o
> EventSystem.o EventSystem.cc &&\
> mv -f $depbase.Tpo $depbase.Po
> ...
> make[4]: Entering directory
> '/home/arno/trafficserver/trafficserver/lib/luajit'
> Building LuaJIT 2.0.3
> make -C src
> make[5]: Entering directory
> '/home/arno/trafficserver/trafficserver/lib/luajit/src'
> HOSTCChost/minilua.o
> HOSTLINK host/minilua
> DYNASMhost/buildvm_arch.h
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (TS-2917) luajit ignores --disable-silent-rules
[
https://issues.apache.org/jira/browse/TS-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053191#comment-14053191
]
Leif Hedstrom edited comment on TS-2917 at 7/6/14 7:07 PM:
---
Looks like we could maybe do make Q="" on the LuaJIT build? But, we'd somehow
need to pass this down from the configure setting?
was (Author: zwoop):
Looks like we could maybe do make Q="" on the LuaJIT build?
> luajit ignores --disable-silent-rules
> -
>
> Key: TS-2917
> URL: https://issues.apache.org/jira/browse/TS-2917
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
>Reporter: Arno Toell
>Priority: Minor
> Fix For: 5.1.0
>
>
> When compiling ATS with --disable-silent-rules the luajit tree ignores that
> configure flag. Excerpt:
> {code}
> ./configure --enable-layout=Debian --sysconfdir=/etc/trafficserver
> --libdir=/usr/lib/trafficserver --with-user=root --with-group=root
> --disable-silent-rules --enable-experimental-plugins
> --enable-reclaimable-freelist CFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security"
> CPPFLAGS="-D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security" FCFLAGS="-g -O2
> -fstack-protector --param=ssp-buffer-size=4" FFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4" GCJFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4" LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security"
> OBJCXXFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
> -Werror=format-security" --enable-wccp --enable-linux-native-aio
> ...
> make[3]: Entering directory
> '/home/arno/trafficserver/trafficserver/iocore/eventsystem'
> depbase=`echo EventSystem.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
> c++ -DHAVE_CONFIG_H -I. -I../../lib/ts -I../../lib -I../../lib/records
> -I../../lib/ts -D_FORTIFY_SOURCE=2 -Dlinux -D_LARGEFILE64_SOURCE=1
> -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -I/usr/include/tcl8.6
> -I/usr/include/libxml2 -Wunused-parameter -g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++11 -pipe
> -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing
> -Wno-invalid-offsetof -mcx16 -MT EventSystem.o -MD -MP -MF $depbase.Tpo -c -o
> EventSystem.o EventSystem.cc &&\
> mv -f $depbase.Tpo $depbase.Po
> ...
> make[4]: Entering directory
> '/home/arno/trafficserver/trafficserver/lib/luajit'
> Building LuaJIT 2.0.3
> make -C src
> make[5]: Entering directory
> '/home/arno/trafficserver/trafficserver/lib/luajit/src'
> HOSTCChost/minilua.o
> HOSTLINK host/minilua
> DYNASMhost/buildvm_arch.h
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2917) luajit ignores --disable-silent-rules
[
https://issues.apache.org/jira/browse/TS-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2917:
--
Assignee: Arno Toell
> luajit ignores --disable-silent-rules
> -
>
> Key: TS-2917
> URL: https://issues.apache.org/jira/browse/TS-2917
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
>Reporter: Arno Toell
>Assignee: Arno Toell
>Priority: Minor
> Fix For: 5.1.0
>
>
> When compiling ATS with --disable-silent-rules the luajit tree ignores that
> configure flag. Excerpt:
> {code}
> ./configure --enable-layout=Debian --sysconfdir=/etc/trafficserver
> --libdir=/usr/lib/trafficserver --with-user=root --with-group=root
> --disable-silent-rules --enable-experimental-plugins
> --enable-reclaimable-freelist CFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security"
> CPPFLAGS="-D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security" FCFLAGS="-g -O2
> -fstack-protector --param=ssp-buffer-size=4" FFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4" GCJFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4" LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security"
> OBJCXXFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
> -Werror=format-security" --enable-wccp --enable-linux-native-aio
> ...
> make[3]: Entering directory
> '/home/arno/trafficserver/trafficserver/iocore/eventsystem'
> depbase=`echo EventSystem.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
> c++ -DHAVE_CONFIG_H -I. -I../../lib/ts -I../../lib -I../../lib/records
> -I../../lib/ts -D_FORTIFY_SOURCE=2 -Dlinux -D_LARGEFILE64_SOURCE=1
> -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -I/usr/include/tcl8.6
> -I/usr/include/libxml2 -Wunused-parameter -g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++11 -pipe
> -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing
> -Wno-invalid-offsetof -mcx16 -MT EventSystem.o -MD -MP -MF $depbase.Tpo -c -o
> EventSystem.o EventSystem.cc &&\
> mv -f $depbase.Tpo $depbase.Po
> ...
> make[4]: Entering directory
> '/home/arno/trafficserver/trafficserver/lib/luajit'
> Building LuaJIT 2.0.3
> make -C src
> make[5]: Entering directory
> '/home/arno/trafficserver/trafficserver/lib/luajit/src'
> HOSTCChost/minilua.o
> HOSTLINK host/minilua
> DYNASMhost/buildvm_arch.h
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2917) luajit ignores --disable-silent-rules
[
https://issues.apache.org/jira/browse/TS-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053192#comment-14053192
]
Leif Hedstrom commented on TS-2917:
---
I.e. something in the line of
{code}
diff --git a/lib/Makefile.am b/lib/Makefile.am
index ab09752..df5c255 100644
--- a/lib/Makefile.am
+++ b/lib/Makefile.am
@@ -49,7 +49,7 @@ all-local:
test -d "$(top_srcdir)/$(subdir)/luajit/src" || (cd "$(top_srcdir)" &&
git submodule update --init)
test -d "$(top_builddir)/$(subdir)/luajit/src" || cp -rf
"$(srcdir)/luajit" "$(top_builddir)/$(subdir)/"
cd luajit && $(MAKE) $(AM_MAKEFLAGS) BUILDMODE="static"
PREFIX="$(prefix)" CC="$(CC)" \
-CFLAGS="$(LUA_CFLAGS)" LDFLAGS="@LUA_LDFLAGS@"
+CFLAGS="$(LUA_CFLAGS)" LDFLAGS="@LUA_LDFLAGS@" Q=""
clean-local:
test "$(top_srcdir)" != "$(top_builddir)" || (cd
"$(top_builddir)/$(subdir)/luajit" && make clean)
{code}
But, conditionally on the V=1 or --disable-slient-rules configure option.
> luajit ignores --disable-silent-rules
> -
>
> Key: TS-2917
> URL: https://issues.apache.org/jira/browse/TS-2917
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
>Reporter: Arno Toell
>Assignee: Arno Toell
>Priority: Minor
> Fix For: 5.1.0
>
>
> When compiling ATS with --disable-silent-rules the luajit tree ignores that
> configure flag. Excerpt:
> {code}
> ./configure --enable-layout=Debian --sysconfdir=/etc/trafficserver
> --libdir=/usr/lib/trafficserver --with-user=root --with-group=root
> --disable-silent-rules --enable-experimental-plugins
> --enable-reclaimable-freelist CFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security"
> CPPFLAGS="-D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security" FCFLAGS="-g -O2
> -fstack-protector --param=ssp-buffer-size=4" FFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4" GCJFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4" LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security"
> OBJCXXFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
> -Werror=format-security" --enable-wccp --enable-linux-native-aio
> ...
> make[3]: Entering directory
> '/home/arno/trafficserver/trafficserver/iocore/eventsystem'
> depbase=`echo EventSystem.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
> c++ -DHAVE_CONFIG_H -I. -I../../lib/ts -I../../lib -I../../lib/records
> -I../../lib/ts -D_FORTIFY_SOURCE=2 -Dlinux -D_LARGEFILE64_SOURCE=1
> -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -I/usr/include/tcl8.6
> -I/usr/include/libxml2 -Wunused-parameter -g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++11 -pipe
> -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing
> -Wno-invalid-offsetof -mcx16 -MT EventSystem.o -MD -MP -MF $depbase.Tpo -c -o
> EventSystem.o EventSystem.cc &&\
> mv -f $depbase.Tpo $depbase.Po
> ...
> make[4]: Entering directory
> '/home/arno/trafficserver/trafficserver/lib/luajit'
> Building LuaJIT 2.0.3
> make -C src
> make[5]: Entering directory
> '/home/arno/trafficserver/trafficserver/lib/luajit/src'
> HOSTCChost/minilua.o
> HOSTLINK host/minilua
> DYNASMhost/buildvm_arch.h
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2917) luajit ignores --disable-silent-rules
[
https://issues.apache.org/jira/browse/TS-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2917:
--
Fix Version/s: 5.1.0
> luajit ignores --disable-silent-rules
> -
>
> Key: TS-2917
> URL: https://issues.apache.org/jira/browse/TS-2917
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
>Reporter: Arno Toell
>Priority: Minor
> Fix For: 5.1.0
>
>
> When compiling ATS with --disable-silent-rules the luajit tree ignores that
> configure flag. Excerpt:
> {code}
> ./configure --enable-layout=Debian --sysconfdir=/etc/trafficserver
> --libdir=/usr/lib/trafficserver --with-user=root --with-group=root
> --disable-silent-rules --enable-experimental-plugins
> --enable-reclaimable-freelist CFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security"
> CPPFLAGS="-D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security" FCFLAGS="-g -O2
> -fstack-protector --param=ssp-buffer-size=4" FFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4" GCJFLAGS="-g -O2 -fstack-protector
> --param=ssp-buffer-size=4" LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security"
> OBJCXXFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
> -Werror=format-security" --enable-wccp --enable-linux-native-aio
> ...
> make[3]: Entering directory
> '/home/arno/trafficserver/trafficserver/iocore/eventsystem'
> depbase=`echo EventSystem.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
> c++ -DHAVE_CONFIG_H -I. -I../../lib/ts -I../../lib -I../../lib/records
> -I../../lib/ts -D_FORTIFY_SOURCE=2 -Dlinux -D_LARGEFILE64_SOURCE=1
> -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -I/usr/include/tcl8.6
> -I/usr/include/libxml2 -Wunused-parameter -g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++11 -pipe
> -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing
> -Wno-invalid-offsetof -mcx16 -MT EventSystem.o -MD -MP -MF $depbase.Tpo -c -o
> EventSystem.o EventSystem.cc &&\
> mv -f $depbase.Tpo $depbase.Po
> ...
> make[4]: Entering directory
> '/home/arno/trafficserver/trafficserver/lib/luajit'
> Building LuaJIT 2.0.3
> make -C src
> make[5]: Entering directory
> '/home/arno/trafficserver/trafficserver/lib/luajit/src'
> HOSTCChost/minilua.o
> HOSTLINK host/minilua
> DYNASMhost/buildvm_arch.h
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2920) Stale_While_revalidate
[ https://issues.apache.org/jira/browse/TS-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2920: -- Labels: crash (was: ) > Stale_While_revalidate > -- > > Key: TS-2920 > URL: https://issues.apache.org/jira/browse/TS-2920 > Project: Traffic Server > Issue Type: Bug > Components: Performance, Plugins >Reporter: Faysal Banna > Labels: crash > Fix For: sometime > > > trafficserver 5.0.0 release version > FATAL: InkAPI.cc:2670: failed assert `sdk_sanity_check_mbuffer(bufp) == > TS_SUCCESS` > /usr/local/bin/traffic_server - STACK TRACE: > /usr/local/lib/libtsutil.so.5(+0x1e3a7)[0x2b6db45e93a7] > /usr/local/lib/libtsutil.so.5(+0x1e3a7)[0x2b6db45e93a7] > /usr/local/lib/libtsutil.so.5(+0x1d45f)[0x2b6db45e845f] > /usr/local/lib/libtsutil.so.5(+0x1d45f)[0x2b6db45e845f] > /usr/local/bin/traffic_server(TSMimeHdrFieldFind+0x2f)[0x4ba43f] > /usr/local/libexec/trafficserver/stale_while_revalidate.so(+0x308a)[0x2b6dbb98308a] > /usr/local/bin/traffic_server(EThread::process_event(Event*, > int)+0x170)[0x737210] > /usr/local/bin/traffic_server(TSMimeHdrFieldFind+0x2f)[0x4ba43f] > /usr/local/bin/traffic_server(EThread::execute()+0x793)[0x737de3] > /usr/local/libexec/trafficserver/stale_while_revalidate.so(+0x308a)[0x2b6dbb98308a] > /usr/local/bin/traffic_server[0x736b5a] > /usr/local/bin/traffic_server(EThread::process_event(Event*, > int)+0x170)[0x737210] > /lib64/libpthread.so.0(+0x7f33)[0x2b6db60a2f33] > /usr/local/bin/traffic_server(EThread::execute()+0x793)[0x737de3] > /lib64/libc.so.6(clone+0x6d)[0x2b6db713eded] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2918) collapsed_connection Plugin Errors
[ https://issues.apache.org/jira/browse/TS-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2918: -- Fix Version/s: sometime > collapsed_connection Plugin Errors > --- > > Key: TS-2918 > URL: https://issues.apache.org/jira/browse/TS-2918 > Project: Traffic Server > Issue Type: Bug > Components: Performance, Plugins >Reporter: Faysal Banna > Labels: crash > Fix For: sometime > > > Hi Guys. > I been using trafficserver for over a year with all the good stuff it holds > still there are bugs that are yet not fixed > one of the common bug in a plugin experimental called collapsed_connection > and here's the output > FATAL: InkAPI.cc:989: failed assert `!"Plugin tries to use a continuation > which is deleted"` > /usr/local/bin/traffic_server - STACK TRACE: > /usr/local/lib/libtsutil.so.5(+0x1e897)[0x2b587580c897] > /usr/local/lib/libtsutil.so.5(+0x1d84f)[0x2b587580b84f] > /usr/local/bin/traffic_server[0x4b73b3] > /usr/local/bin/traffic_server(HttpSM::state_api_callout(int, > void*)+0x102)[0x5ae762] > /usr/local/bin/traffic_server(HttpSM::state_cache_open_read(int, > void*)+0x170)[0x5af510] > /usr/local/bin/traffic_server(HttpSM::main_handler(int, void*)+0xbd)[0x5b319d] > /usr/local/bin/traffic_server(HttpCacheSM::state_cache_open_read(int, > void*)+0x156)[0x5910c6] > /usr/local/bin/traffic_server(Cache::open_read(Continuation*, INK_MD5*, > HTTPHdr*, CacheLookupHttpConfig*, CacheFragType, char*, int)+0x642)[0x6dfd12] > /usr/local/bin/traffic_server(CacheProcessor::open_read(Continuation*, URL*, > bool, HTTPHdr*, CacheLookupHttpConfig*, long, CacheFragType)+0x9b)[0x6beecb] > /usr/local/bin/traffic_server(HttpCacheSM::open_read(URL*, HTTPHdr*, > CacheLookupHttpConfig*, long)+0x81)[0x591381] > /usr/local/bin/traffic_server(HttpSM::do_cache_lookup_and_read()+0xfb)[0x5a163b] > /usr/local/bin/traffic_server(HttpSM::set_next_state()+0x7aa)[0x5b3c2a] > /usr/local/bin/traffic_server(HttpSM::state_api_callout(int, > void*)+0x2c0)[0x5ae920] > /usr/local/bin/traffic_server(HttpSM::state_api_callback(int, > void*)+0x82)[0x5b3382] > /usr/local/bin/traffic_server(TSHttpTxnReenable+0x244)[0x4c9c34] > /usr/local/libexec/trafficserver/collapsed_connection.so(+0x2edf)[0x2b587b651edf] > /usr/local/libexec/trafficserver/collapsed_connection.so(+0x4714)[0x2b587b653714] > /usr/local/libexec/trafficserver/collapsed_connection.so(+0x4b90)[0x2b587b653b90] > /usr/local/bin/traffic_server(EThread::process_event(Event*, > int)+0x170)[0x73e030] > /usr/local/bin/traffic_server(EThread::execute()+0x7e1)[0x73ec51] > /usr/local/bin/traffic_server[0x73d94a] > each time this happens the server is being restarted > much regards -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2920) Stale_While_revalidate
[ https://issues.apache.org/jira/browse/TS-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2920: -- Fix Version/s: sometime > Stale_While_revalidate > -- > > Key: TS-2920 > URL: https://issues.apache.org/jira/browse/TS-2920 > Project: Traffic Server > Issue Type: Bug > Components: Performance, Plugins >Reporter: Faysal Banna > Labels: crash > Fix For: sometime > > > trafficserver 5.0.0 release version > FATAL: InkAPI.cc:2670: failed assert `sdk_sanity_check_mbuffer(bufp) == > TS_SUCCESS` > /usr/local/bin/traffic_server - STACK TRACE: > /usr/local/lib/libtsutil.so.5(+0x1e3a7)[0x2b6db45e93a7] > /usr/local/lib/libtsutil.so.5(+0x1e3a7)[0x2b6db45e93a7] > /usr/local/lib/libtsutil.so.5(+0x1d45f)[0x2b6db45e845f] > /usr/local/lib/libtsutil.so.5(+0x1d45f)[0x2b6db45e845f] > /usr/local/bin/traffic_server(TSMimeHdrFieldFind+0x2f)[0x4ba43f] > /usr/local/libexec/trafficserver/stale_while_revalidate.so(+0x308a)[0x2b6dbb98308a] > /usr/local/bin/traffic_server(EThread::process_event(Event*, > int)+0x170)[0x737210] > /usr/local/bin/traffic_server(TSMimeHdrFieldFind+0x2f)[0x4ba43f] > /usr/local/bin/traffic_server(EThread::execute()+0x793)[0x737de3] > /usr/local/libexec/trafficserver/stale_while_revalidate.so(+0x308a)[0x2b6dbb98308a] > /usr/local/bin/traffic_server[0x736b5a] > /usr/local/bin/traffic_server(EThread::process_event(Event*, > int)+0x170)[0x737210] > /lib64/libpthread.so.0(+0x7f33)[0x2b6db60a2f33] > /usr/local/bin/traffic_server(EThread::execute()+0x793)[0x737de3] > /lib64/libc.so.6(clone+0x6d)[0x2b6db713eded] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2918) collapsed_connection Plugin Errors
[ https://issues.apache.org/jira/browse/TS-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2918: -- Labels: crash (was: ) > collapsed_connection Plugin Errors > --- > > Key: TS-2918 > URL: https://issues.apache.org/jira/browse/TS-2918 > Project: Traffic Server > Issue Type: Bug > Components: Performance, Plugins >Reporter: Faysal Banna > Labels: crash > Fix For: sometime > > > Hi Guys. > I been using trafficserver for over a year with all the good stuff it holds > still there are bugs that are yet not fixed > one of the common bug in a plugin experimental called collapsed_connection > and here's the output > FATAL: InkAPI.cc:989: failed assert `!"Plugin tries to use a continuation > which is deleted"` > /usr/local/bin/traffic_server - STACK TRACE: > /usr/local/lib/libtsutil.so.5(+0x1e897)[0x2b587580c897] > /usr/local/lib/libtsutil.so.5(+0x1d84f)[0x2b587580b84f] > /usr/local/bin/traffic_server[0x4b73b3] > /usr/local/bin/traffic_server(HttpSM::state_api_callout(int, > void*)+0x102)[0x5ae762] > /usr/local/bin/traffic_server(HttpSM::state_cache_open_read(int, > void*)+0x170)[0x5af510] > /usr/local/bin/traffic_server(HttpSM::main_handler(int, void*)+0xbd)[0x5b319d] > /usr/local/bin/traffic_server(HttpCacheSM::state_cache_open_read(int, > void*)+0x156)[0x5910c6] > /usr/local/bin/traffic_server(Cache::open_read(Continuation*, INK_MD5*, > HTTPHdr*, CacheLookupHttpConfig*, CacheFragType, char*, int)+0x642)[0x6dfd12] > /usr/local/bin/traffic_server(CacheProcessor::open_read(Continuation*, URL*, > bool, HTTPHdr*, CacheLookupHttpConfig*, long, CacheFragType)+0x9b)[0x6beecb] > /usr/local/bin/traffic_server(HttpCacheSM::open_read(URL*, HTTPHdr*, > CacheLookupHttpConfig*, long)+0x81)[0x591381] > /usr/local/bin/traffic_server(HttpSM::do_cache_lookup_and_read()+0xfb)[0x5a163b] > /usr/local/bin/traffic_server(HttpSM::set_next_state()+0x7aa)[0x5b3c2a] > /usr/local/bin/traffic_server(HttpSM::state_api_callout(int, > void*)+0x2c0)[0x5ae920] > /usr/local/bin/traffic_server(HttpSM::state_api_callback(int, > void*)+0x82)[0x5b3382] > /usr/local/bin/traffic_server(TSHttpTxnReenable+0x244)[0x4c9c34] > /usr/local/libexec/trafficserver/collapsed_connection.so(+0x2edf)[0x2b587b651edf] > /usr/local/libexec/trafficserver/collapsed_connection.so(+0x4714)[0x2b587b653714] > /usr/local/libexec/trafficserver/collapsed_connection.so(+0x4b90)[0x2b587b653b90] > /usr/local/bin/traffic_server(EThread::process_event(Event*, > int)+0x170)[0x73e030] > /usr/local/bin/traffic_server(EThread::execute()+0x7e1)[0x73ec51] > /usr/local/bin/traffic_server[0x73d94a] > each time this happens the server is being restarted > much regards -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2802) Add SNI support for origin servers
[
https://issues.apache.org/jira/browse/TS-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053303#comment-14053303
]
James Peach commented on TS-2802:
-
{quote}
1. ./lib/ts/ink_memory.h: #define ats_strndup(p,n) _xstrdup((p), n, NULL).
{quote}
Yup, which is why all code should use {{ats_strndup}}.
{quote}
2. Looks like NetVCOptions includes a few basic protocol & sockets attributes
that are user options and convenient to be assigned, servername seems to be
more reasonable to attach to a client vc, any concerns to alter the interface?
{quote}
No, I don't think that the {{NetVConnection}} interface should be changed for
this. {{NetVCOptions}} is still my preferred solution, though I'm not saying
that you should attach the whole thing to the {{SSLNetVConnection}}. Another
solution could be to add an SSL-extended version of {{connect_re}} to the
{{SSLNetProcessor}} to carry SSL-specific options.
> Add SNI support for origin servers
> --
>
> Key: TS-2802
> URL: https://issues.apache.org/jira/browse/TS-2802
> Project: Traffic Server
> Issue Type: Improvement
> Components: SSL
>Reporter: Bryan Call
>Assignee: Bryan Call
> Labels: Review
> Fix For: 5.1.0
>
> Attachments: TS-2802.diff
>
>
> test to an origin that requires SNI
> {code}
> [bcall@cat ~]$ tail -1 /usr/local/etc/trafficserver/remap.config
> map http://foo.yahoo.com
> https://www.mnot.net/blog/2014/05/09/if_you_can_read_this_youre_sniing
> [bcall@cat ~]$ curl -H 'Host: foo.yahoo.com' http://localhost:8080/; echo
> TLS SNI Required.
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (TS-2921) Build failure is caused by mismatching types
Ryo Okubo created TS-2921:
-
Summary: Build failure is caused by mismatching types
Key: TS-2921
URL: https://issues.apache.org/jira/browse/TS-2921
Project: Traffic Server
Issue Type: Bug
Components: Build
Reporter: Ryo Okubo
After modification of TS-2893 merged, build failure is occured as below log.
{noformat}
SSLUtils.cc: In function 'SSL_CTX* SSLInitServerContext(const SSLConfigParams*,
const ssl_user_config&)':
SSLUtils.cc:976: error: operands to ?: have different types 'const xptr'
and 'const char [1]'
SSLUtils.cc:986: warning: too many arguments for format
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2921) Build failure is caused by mismatching types
[
https://issues.apache.org/jira/browse/TS-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryo Okubo updated TS-2921:
--
Attachment: fix_sslutils.diff
> Build failure is caused by mismatching types
>
>
> Key: TS-2921
> URL: https://issues.apache.org/jira/browse/TS-2921
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
>Reporter: Ryo Okubo
> Attachments: fix_sslutils.diff
>
>
> After modification of TS-2893 merged, build failure is occured as below log.
> {noformat}
> SSLUtils.cc: In function 'SSL_CTX* SSLInitServerContext(const
> SSLConfigParams*, const ssl_user_config&)':
> SSLUtils.cc:976: error: operands to ?: have different types 'const
> xptr' and 'const char [1]'
> SSLUtils.cc:986: warning: too many arguments for format
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2921) Build failure is caused by mismatching types
[
https://issues.apache.org/jira/browse/TS-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryo Okubo updated TS-2921:
--
Attachment: (was: fix_sslutils.diff)
> Build failure is caused by mismatching types
>
>
> Key: TS-2921
> URL: https://issues.apache.org/jira/browse/TS-2921
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
>Reporter: Ryo Okubo
>
> After modification of TS-2893 merged, build failure is occured as below log.
> {noformat}
> SSLUtils.cc: In function 'SSL_CTX* SSLInitServerContext(const
> SSLConfigParams*, const ssl_user_config&)':
> SSLUtils.cc:976: error: operands to ?: have different types 'const
> xptr' and 'const char [1]'
> SSLUtils.cc:986: warning: too many arguments for format
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
