Bug#854551: 400 errors caused by 7.0.28-4+deb7u10
Allen Hadden
ahadden at us.ibm.com
Thu Feb 16 22:39:51 UTC 2017
The plot thickens! I created a local build from git using the
7.0.28-4+deb7u10 tag. Interestingly when I did that I was unable to
reproduce the problem. Originally I suspected that there was something
wrong with my build. But after some digging, I'm starting to suspect the
official build. Here's why...
Note that I have 7.0.28-4+deb7u10 installed on my system:
$ dpkg-query -W -f '${Version}\n' libtomcat7-java
7.0.28-4+deb7u10
Also that tomcat-coyote.jar is from that package:
$ dpkg-query -L libtomcat7-java | grep tomcat-coyote.jar
/usr/share/java/tomcat-coyote.jar
/usr/share/tomcat7/lib/tomcat-coyote.jar
(The first one is a symlink to the second one.)
I have attached two files, dist-tomcat-coyote-contents.txt and
built-tomcat-coyote-contents.txt. These files just contain the output of
"unzip -t tomcat-coyote.jar". Note that I chose that file because it
contains the AbstractInputBuffer class. I expected there to be no
differences. However, a diff of those files shows this:
$ diff dist-tomcat-coyote-contents.txt built-tomcat-coyote-contents.txt
1c1
< Archive: /usr/share/tomcat7/lib/tomcat-coyote.jar
---
> Archive: built-tomcat7-7.0.28-4+deb7u10/tomcat-coyote.jar
18,20d17
< testing: org/apache/tomcat/util/codec/ OK
< testing: org/apache/tomcat/util/codec/binary/ OK
< testing: org/apache/tomcat/util/collections/ OK
37d33
< testing: org/apache/tomcat/util/security/ OK
122d117
< testing: org/apache/coyote/http11/filters/LocalStrings.properties OK
270,280d264
< testing: org/apache/tomcat/util/codec/BinaryDecoder.class OK
< testing: org/apache/tomcat/util/codec/BinaryEncoder.class OK
< testing: org/apache/tomcat/util/codec/Decoder.class OK
< testing: org/apache/tomcat/util/codec/DecoderException.class OK
< testing: org/apache/tomcat/util/codec/Encoder.class OK
< testing: org/apache/tomcat/util/codec/EncoderException.class OK
< testing: org/apache/tomcat/util/codec/binary/Base64.class OK
< testing:
org/apache/tomcat/util/codec/binary/BaseNCodec$Context.class OK
< testing: org/apache/tomcat/util/codec/binary/BaseNCodec.class OK
< testing: org/apache/tomcat/util/codec/binary/StringUtils.class OK
< testing: org/apache/tomcat/util/collections/ConcurrentCache.class OK
381c365,370
< testing:
org/apache/tomcat/util/http/parser/HttpParser$SkipConstantResult.class OK
---
> testing: org/apache/tomcat/util/http/parser/AstAttribute.class OK
> testing: org/apache/tomcat/util/http/parser/AstMediaType.class OK
> testing: org/apache/tomcat/util/http/parser/AstParameter.class OK
> testing: org/apache/tomcat/util/http/parser/AstSubType.class OK
> testing: org/apache/tomcat/util/http/parser/AstType.class OK
> testing: org/apache/tomcat/util/http/parser/AstValue.class OK
383,384c372,381
< testing: org/apache/tomcat/util/http/parser/MediaType.class OK
< testing: org/apache/tomcat/util/http/parser/MediaTypeCache.class OK
---
> testing:
org/apache/tomcat/util/http/parser/HttpParserConstants.class OK
> testing:
org/apache/tomcat/util/http/parser/HttpParserTokenManager.class OK
> testing:
org/apache/tomcat/util/http/parser/HttpParserTreeConstants.class OK
> testing: org/apache/tomcat/util/http/parser/JJTHttpParserState.class
OK
> testing: org/apache/tomcat/util/http/parser/Node.class OK
> testing: org/apache/tomcat/util/http/parser/ParseException.class OK
> testing: org/apache/tomcat/util/http/parser/SimpleCharStream.class
OK
> testing: org/apache/tomcat/util/http/parser/SimpleNode.class OK
> testing: org/apache/tomcat/util/http/parser/Token.class OK
> testing: org/apache/tomcat/util/http/parser/TokenMgrError.class OK
482,484d478
< testing: org/apache/tomcat/util/security/PermissionCheck.class OK
< testing: org/apache/tomcat/util/security/PrivilegedGetTccl.class OK
< testing: org/apache/tomcat/util/security/PrivilegedSetTccl.class OK
498c492
< No errors detected in compressed data of
/usr/share/tomcat7/lib/tomcat-coyote.jar.
---
> No errors detected in compressed data of
built-tomcat7-7.0.28-4+deb7u10/tomcat-coyote.jar.
The interesting thing about this to me is that some of those class files
are supposed to be only in Tomcat 8 and not in Tomcat 7 (or only in Tomcat
7 and not in Tomcat 8).
Is it possible that the build wasn't "clean" in that it contained some
Tomcat 8 class files? It certainly smells like that.
Thanks,
Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20170216/bc95d1f2/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dist-tomcat-coyote-contents.txt
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20170216/bc95d1f2/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: built-tomcat-coyote-contents.txt
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20170216/bc95d1f2/attachment-0003.txt>
More information about the pkg-java-maintainers
mailing list