-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David,
On 10/15/12 2:04 PM, David Wall wrote: > In researching a bug our users are now suffering, I found that it > was reported already as *Bug 53814****- Could not display PDF file > on Tomcat 7.0.27 above.* > > Sadly, it also shows that's it's considered "invalid" and won't be > fixed because the change made between 7.0.26 and 7.0.27 is > "standards compliant." > > That's a rather unsatisfying answer considering it affects PDFs and > IE, a rather common combination. You didn't like the answer "file a separate enhancement request and we'll handle that separately"? If you can't be bothered to file an enhancement request then how do you expect anyone to bother to "fix" this? > The change was made in the 7.0.27 release, causing the bug to > appear. Yes, the bug is in fact in the PDF reader of IE, but it is > sad when a bug release (not going from 7.0 to 7.1, but 7.0.26 to > 7.0.27) introduces new problems. By all means, downgrade. Unfortunately, you'll have to suffer all the regressions where fixed bugs make the new versions of Tomcat incompatible with old versions. All new releases could potentially introduce new "problems". This new behavior is not a regression. It is standards-compliant. The client is broken. Anyone can write a broken client. Should Tomcat implement fixes for all broken clients? > Putting the space separator back in seems so straightforward > unless removing the space actually fixes something else. Care to test with all clients and get back to us? This is what standards are for. You're right: the change is straightforward. So is filing an enhancement request. > It is not clear in the bug report if the change was made for a > particular reason or not since bug 52811 doesn't appear to be an > issue with 'boundary' at all. > > It is not clear that having the space would not be compliant with > the spec. The comment in the bug report even says that all of the > examples in the specification have a whitespace before parameter. There is no argument whether the space would or not be a spec violation. The question is why the Adobe PDF plug-in requires the space to be there (which is not compliant). > I guess I can understand a change like this that will break > working systems if the change were required to be standards > compliant and standards-compliant browsers had trouble because of > the space being there, but if not, it shouldn't occur in such a > late patch release (7.0.27) rather than a new minor release like > 7.1. I think you're being overly sensitive. You can't expect Tomcat to fix (or break) nothing between 7.0 and 7.1. > I hope that keeping things working is the prevailing idea behind > patch releases. Of course, it's not surprising that IE would be > the one browser to have this problem handling standards-compliant > syntax! It's not MSIE's fault, here. It's the PDF plug-in from Adobe (who often takes liberties with standards as well). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB8Yx8ACgkQ9CaO5/Lv0PB70ACdEFoeioV0vxwB9VBP7vmtIiG2 rr8AnihXgHID3h3l/Grj4ZZub+Tbeq65 =4DLC -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
