DO NOT REPLY [Bug 37018] New: - Document how to use tomcat-SSL with a pkcs11 token
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=37018. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=37018 Summary: Document how to use tomcat-SSL with a pkcs11 token Product: Tomcat 5 Version: 5.5.9 Platform: Other URL: http://java.sun.com/j2se/1.5.0/docs/guide/security/p11gu ide.html OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: Connector:Coyote AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Since jdk1.5 has a sun.security.pkcs11.SunPKCS11 implementing java.security.Provider, it should be possible to no longer store private keys on the server computer's harddisk, but on a USB token or alike (being willing to accept that SSL may become very slow...) Others appear to have asked for this http://marc.theaimsgroup.com/?l=tomcat-userm=111471470228516w=2 more also in http://forum.java.sun.com/thread.jspa?threadID=256018messageID=3838346 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 36574] New: - Broken PDF document in online docware
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36574. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36574 Summary: Broken PDF document in online docware Product: Tomcat 5 Version: 5.5.9 Platform: All URL: http://jakarta.apache.org/tomcat/tomcat-5.5- doc/architecture/startup.html OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Unknown AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Hope this is the right place to report ... On the page http://jakarta.apache.org/tomcat/tomcat-5.5-doc/architecture/startup.html there is a link UML sequence diagram of the startup procedure is available here pointing to http://jakarta.apache.org/tomcat/tomcat-5.5-doc/architecture/startup/serverStartup.pdf. That PDF document is broken. When trying to open with Adobe Reader 7.0.1 on Windows 2000 it says An unrecognized token .P35.76 was found. When trying with xpdf or acroread on Linux I get similar results; the document cannot be viewed. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35725. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35725 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-07-14 21:04 --- Entity resolution is done at translation time (as required by the spec), so all entity definitions must be available then. Since you almost certainly don't want nbsp;, gt;, lt;, etc. to be resolved at translation time, you need to quote them in the source either in a CDATA section or as amp;nbsp;. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35725. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35725 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35725. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35725 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2005-07-15 02:41 --- I'm still unclear about something. - You said Entity resolution is done at translation time (as required by the spec),, could you provide us which spec and where( i.e. which section ) has this requirement ? - Current jasper can resolve some entities(lt;, gt;, quot;, amp;, apos; ). I'd like to know why. If what you said is correct, they should be also flagged as an error. Why I'm asking is that I'd like to know how to have Jasper recognize additional entities. ( adding something to jsp:root tag ? or something like that. ) - When I tried the syntax #D;, jasper seems to recognize it. (Note that according to HTML spec, this syntax is valid. ) Is this shure that this syntax is also runnable for jasper ? Why I'm asking these is that current jasper accepts some entities while it doesn't accept others so I'm wondering what is the threshold for jasper to accept/not accept entities. Thank you very much. . . -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35725. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35725 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-07-15 05:08 --- (In reply to comment #4) I'm still unclear about something. - You said Entity resolution is done at translation time (as required by the spec),, could you provide us which spec and where( i.e. which section ) has this requirement ? spec-quote spec=JSP version=2.0 section=6.2.3 The first step in processing a JSP document is to process it as an XML document, checking for well-formedness, processing entity resolution and, if applicable, performing validation as described in Section JSP.6.2.4. /spec-quote - Current jasper can resolve some entities(lt;, gt;, quot;, amp;, apos; ). I'd like to know why. If what you said is correct, they should be also flagged as an error. Why I'm asking is that I'd like to know how to have Jasper recognize additional entities. ( adding something to jsp:root tag ? or something like that. ) Doh, those are standard XML entities that all XML parsers recognize. Use them in (without escaping) your JSPX page, and you're toast ;-). Watch your browser choke on: jsp:root xmlns:jsp==http://java.sun.com/JSP/Page; version=2.0 jsp:output omit-xml-declaration=no doctype-root-element=html doctype-public=-//W3C//DTD XHTML 1.1//EN doctype-system=http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd/ html bodyHello lt;World/body /html /jsp:root - When I tried the syntax #D;, jasper seems to recognize it. (Note that according to HTML spec, this syntax is valid. ) Is this shure that this syntax is also runnable for jasper ? Again, a standard XML entity. Why I'm asking these is that current jasper accepts some entities while it doesn't accept others so I'm wondering what is the threshold for jasper to accept/not accept entities. It's really simple: Jasper accepts the standard XML entities, as well as those defined in the internal and/or external DTD of the source document. And, of course, DTD declarations buried in CDATA sections don't count (they are nothing more than text Strings at translation time). But you are really missing the point: You don't want Jasper to resolve the XHTML entities at translation time. Thank you very much. . . -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35725. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35725 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35725] New: - jasper throws org.apache.jasper.JasperException with XHTML document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35725. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35725 Summary: jasper throws org.apache.jasper.JasperException with XHTML document Product: Tomcat 5 Version: 5.5.9 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] When the following XHTML document is accessed through Tomcat, - jsp document - ?xml version=1.0 encoding=ISO-8859-1 ? jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.0 jsp:directive.page language=java contentType=text/html; charset=ISO-8859-1 pageEncoding=ISO-8859-1 / jsp:text ![CDATA[ ?xml version=1.0 encoding=ISO-8859-1 ? ]] /jsp:text jsp:text ![CDATA[ !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1//EN http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd; ]] /jsp:text html xmlns=http://www.w3.org/1999/xhtml; head titlejsp-xhtml.jsp/title /head body pnbsp;/p hr/ p#160;/p hr/ plt;/p hr/ pgt;/p hr/ pquot;/p hr/ pamp;/p hr/ papos;/p /body /html /jsp:root - jsp document - jasper throws the following exception. org.apache.jasper.JasperException: /xml/jsp-xhtml3.jsp(16,12) The entity nbsp was referenced, but not declared. org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:39) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:405) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:86) org.apache.jasper.compiler.JspDocumentParser.parse(JspDocumentParser.java:211) org.apache.jasper.compiler.ParserController.doParse(ParserController.java:196) org.apache.jasper.compiler.ParserController.parse(ParserController.java:100) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:146) org.apache.jasper.compiler.Compiler.compile(Compiler.java:286) org.apache.jasper.compiler.Compiler.compile(Compiler.java:267) org.apache.jasper.compiler.Compiler.compile(Compiler.java:255) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:293) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) but when I removed the line of pnbsp;/p, it works. I'm wondering why jasper accepts : p#160;/p plt;/p pgt;/p pquot;/p pamp;/p papos;/p but doesn't accept pnbsp;/p. All above entitis are valid for XHTML usage. . -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35725. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35725 [EMAIL PROTECTED] changed: What|Removed |Added Severity|normal |critical --- Additional Comments From [EMAIL PROTECTED] 2005-07-14 06:38 --- Changing the severity because this is a runtime problem -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35725. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35725 --- Additional Comments From [EMAIL PROTECTED] 2005-07-14 06:51 --- The other entities defined in - http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent - http://www.w3.org/TR/xhtml1/DTD/xhtml-special.ent - http://www.w3.org/TR/xhtml1/DTD/xhtml-symbol.ent , such as pound; , euro; , hearts; ,Alpha; cause the same exception... Looks like jaspter doesn't take care of entities which are used by XHTML defined in http://www.w3.org/TR/xhtml1/#h-A2 . -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35014] - Please document the change in the context file XML format
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35014. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35014 --- Additional Comments From [EMAIL PROTECTED] 2005-06-01 18:46 --- (In reply to comment #1) Sorry, my fault, I stand corrected re the bold comment - I was focused on the examples at the bottom of the page and skipped over the bold statement at the top of the page. I'd therefore like to file a bug report about my eyeglasses please ;) However despite my failure to read what was there (or perhaps because of it) I would still like to suggest (as also mentioned in report 35055) that it might be useful to put these sorts of issues either in the release notes, or if not appropriate there, to create a new doc at each version called something like Upgrading from previous versions of tomcat...? Such a doc would be a boon for people with existing webapps, to help them make smoother upgrades to later TC builds. Just a suggestion :) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35014] - Please document the change in the context file XML format
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35014. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35014 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-06-01 04:17 --- It's mentioned in bold (and the examples have been updated) in the 5.5. JDBC DataSources How-To. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35014] New: - Please document the change in the context file XML format
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35014. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35014 Summary: Please document the change in the context file XML format Product: Tomcat 5 Version: 5.5.9 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Webapps:Documentation AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Have just spent 3 days stuck on upgrading a working webapp from 5.0.28 to 5.5.9, I finally solved it with help from tomcat-user, but I can't find the core issue mentioned in the TC docs. I therefore humbly suggest it might be a useful note to include in the docs for 5.5 (and maybe 5.0 too, as a warning that the approach that was previously valid in 5.0 is now invalid in 5.5). Also, might it be a good idea to include this in future 5.5.x release notes? Basically, under 5.0.28 I had a separate xml context config file within my warfile/META-INF, that used the nested-tag approach, i.e. ResourceParams parameter /parameter /ResourceParams, but this did not work under 5.5.9, which seems to require the single-tag Resource/ approach. I recognise that the JDBC how-to page example uses the new approach, but it makes no comment about the previous approach being invalid, perhaps it would help those upgrading if the change was explicitly mentioned? I say this particularly in view of the fact that TC offers several ways to config a context, so it might be helpful to clarify that here is one way that is no longer valid in 5.5. The reported exception was No suitable driver from java.sql.DriverManager, which is why I did not initially suspect an XML problem. This is a second reason why this is a tricky one to solve without help from the docs. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34643] - document how to use certificate-based clientAuth on a per user or per session basis also with self-signed/expired client certs
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34643. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34643 --- Additional Comments From [EMAIL PROTECTED] 2005-05-11 15:29 --- Created an attachment (id=14994) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14994action=view) patched SSLAuthenticator.java Thanks to Bill for the help to get it kind of working without the need to configure a realm - how to do this: A) compile the attached and place it in tomcat/server/classes/org/apache/catalina/authenticator/ such that the class-loader finds it before the same one in the catalina.jar B) the web.xml's auth-constraint better has a nested role-name*/role-name otherwise despite a successful hand-shake, the access control will fail the process C) Till now, my browsers (MSIE6 and firefox1.0.3) after one successful login can always login again despite configuring my CSP to prompt for password upon each access to the private key. I attempted to force a re-handshake every time and tried to avoid a server-side caching of the principal/certs, but I didn't succeed so far. Closing the browser after logoff avoids the problem. No clue - perhaps the server is clean and it is the browsers that cache the certs as long as the socket lives due to the HTTP-keep-alive. If it were the servers fault, I guess it would be adequate that a session.invalidate() would also wipe the certs from a previous cert-based authentication. D) If you have multiple private keys and corresponding certificates in your brower's certificate store, the browsers do not offer any self-signed certs to use for client-cert-auth. Haven't tried the remedies brain-stormed in comment 3 item 3, but my suspicion is that this is rather due to browser side implementation. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34643] - document how to use certificate-based clientAuth on a per user or per session basis also with self-signed/expired client certs
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34643. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34643 --- Additional Comments From [EMAIL PROTECTED] 2005-05-11 18:28 --- as per comment 4 item D), got (pseudo-)self signed certs working (it is not the browser's fault), i.e. I first created a self-signed (root9cert), signed the user-cert with it and imported the root-cert into the $JAVA_HOME/jre/lib/security/cacerts for tomcat. Since this doesn't scale as mentioned in and in the described in item 3 GUI/application control flow, the session may well exist before the CLIENT-CERT is executed: i) register trust-store with user-self-signed cert in session for the user to be authenticated as per Bug 34868 ii) response.sendRedirect(/certBasedAuth.do); now that trust-store would be effective upon the subsequent request doing the auth -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34643] - document how to use certificate-based clientAuth on a per user or per session basis also with self-signed/expired client certs
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34643. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34643 [EMAIL PROTECTED] changed: What|Removed |Added Summary|document how to use |document how to use |certificate-based |certificate-based |clientAuth on a per user |clientAuth on a per user |or per session basis|or per session basis also ||with self-signed/expired ||client certs --- Additional Comments From [EMAIL PROTECTED] 2005-05-09 23:49 --- it appears that if the client certificate shall not be asked from all users and not upon the first contact with the given connector, the clientAuth attribute isn't it, irrespective of whether set to true or want. The approach appears to be rather to direct the user to a protected jsp/struts action at the point in time you want the client cert auth to happen with security-constraint web-resource-collection web-resource-nameClient Certificate Auth/web-resource-name url-pattern/certBasedAuth.do/url-pattern /web-resource-collection auth-constraint / /security-constraint login-config auth-methodCLIENT-CERT/auth-method /login-config Being flexible with respect to the used certificate remains tricky: 1) if already knowing the certificate to be expected e.g. by virtue of it being in a LDAP truststore, it appears to be impossible to allow for mismatches of the certs[0].getSubjectDN().getName() without replacing the current org.apache.catalina.authenticator.SSLAuthenticator - one might for example rather use the SHA1 fingerprint to match? 2) similarly, if you want to be more tolerant on certificate expiration/not-yet-valid, I haven't figured how to get the validate=false for org.apache.catalina.realm.RealmBase.authenticate(X509Certificate[] certs) from a config file without altering sources. 3) As for self-signed certificates, I see two approaches a) be able to create a mini-trust-store on the fly before the ssl-handshake occurs in org.apache.tomcat.util.net.jsse.JSSESupport.handShake() - I have no clue how late in an SSLSocket's life its truststore can be altered? A nice example how this can be done a per thread basis (albeit before creating the socket and not when it's already in operation) is Oleg's org.apache.commons.httpclient.contrib.ssl.AuthSSLProtocolSocketFactory (see Bug 34391) - I guess this implies that the web-app programmer in some way (by means of an enhanced LoginConfig or an extra parameter of the method or a session attribute?) might tell org.apache.catalina.authenticator.SSLAuthenticator.authenticate() the self-signed cert it should expect when that method starts b) alternatively, a less rigid TrustManager might be used in org.apache.tomcat.util.net.jsse.JSSE15SocketFactory.getTrustManagers(String keystoreType, String algorithm) - some ideas are in http://forum.java.sun.com/thread.jspa?forumID=2threadID=411937 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34643] New: - document how to use certificate-based clientAuth on a per user or per session basis
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34643. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34643 Summary: document how to use certificate-based clientAuth on a per user or per session basis Product: Tomcat 5 Version: Nightly Build Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Connector:Coyote AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED],[EMAIL PROTECTED] http://jakarta.apache.org/tomcat/tomcat-5.5-doc/ssl-howto.html#Edit%20the%20Tomcat%20Configuration%20File nicely documents how to enable clientAuth on a global basis. A web application may well have a mixed user community, some authenticate by means of a password or other authenticators, others have a certificate for authentication. The goal of this RFE is to amend the documentation with how the clientAuth mechanism can be triggered and enforced on a per user basis. Interim results of my own little research: - if I request org.apache.catalina.Globals.SSL_CERTIFICATE_ATTR, org.apache.coyote.tomcat4.CoyoteRequest.getAttribute triggers the org.apache.coyote.ActionCode.ACTION_REQ_SSL_CERTIFICATE re-handshake - to enforce this for a given user, I guess I could store that certificate in the session and for every subsequent request test whether the cert is stored or otherwise trigger the re-handshake by asking for SSL_CERTIFICATE_ATTR. Open issues I haven't mastered so far: 1) If the application allows for self-signed certificates the user uploads into the DB i.e. her profile, is there a way to use a non-global trustStore to validate? Otherwise, with an increasing user-basis, I foresee scalability problems if I had to import all such certificates into a global trust store? 2) javax.net.ssl.SSLServerSocket.setNeedClientAuth in org.apache.tomcat.util.net.jsse.JSSE14SocketFactory.configureClientAuth might be the basis for an alternative approach, but I wouldn't know how to set that (or probably rather org.apache.tomcat.util.net.ServerSocketFactory.setAttribute(clientAuth, true) before the org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket has already occurred? related mailing list threads probably are: http://marc.theaimsgroup.com/?l=tomcat-userm=105300671215744w=2 and http://marc.theaimsgroup.com/?l=tomcat-userm=104581231518394w=2 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34643] - document how to use certificate-based clientAuth on a per user or per session basis
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34643. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34643 [EMAIL PROTECTED] changed: What|Removed |Added CC|[EMAIL PROTECTED] | --- Additional Comments From [EMAIL PROTECTED] 2005-04-27 21:37 --- (In reply to comment #0) Interim results of my own little research: - if I request org.apache.catalina.Globals.SSL_CERTIFICATE_ATTR, org.apache.coyote.tomcat4.CoyoteRequest.getAttribute triggers the org.apache.coyote.ActionCode.ACTION_REQ_SSL_CERTIFICATE re-handshake This works in 4.1 5.0, but has been removed from 5.5. You would need your own custom Valve to do this in 5.5. Open issues I haven't mastered so far: 1) If the application allows for self-signed certificates the user uploads into the DB i.e. her profile, is there a way to use a non-global trustStore to validate? Otherwise, with an increasing user-basis, I foresee scalability problems if I had to import all such certificates into a global trust store? You probably want an LDAP-based trustStore (e.g. java.security.cert.LDAPCertStoreParameters). Not hard to implement (at least for JDK 1.5), but so far there hasn't been much demand for it. 2) javax.net.ssl.SSLServerSocket.setNeedClientAuth in org.apache.tomcat.util.net.jsse.JSSE14SocketFactory.configureClientAuth might be the basis for an alternative approach, but I wouldn't know how to set that (or probably rather org.apache.tomcat.util.net.ServerSocketFactory.setAttribute(clientAuth, true) before the org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket has already occurred? This is where the clientAuth attribute on the Connector eventually ends up :). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34643] - document how to use certificate-based clientAuth on a per user or per session basis
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34643. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34643 --- Additional Comments From [EMAIL PROTECTED] 2005-04-27 22:07 --- You probably want an LDAP-based trustStore (e.g. java.security.cert.LDAPCertStoreParameters). Not hard to implement (at least for JDK 1.5), but so far there hasn't been much demand for it. I have already done this http://issues.apache.org/bugzilla/show_bug.cgi?id=7831 but I dont know how well this version works. Though I still use it and can reattach my latest version if wanted. I dont understand why there is so little demand for it, but maybe the time for it might come. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Private document
I cannot believe that. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
important document
Please read the attached file! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error in document
Your important document, correction is finished! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Document
Here is the file. --- Trend GateLock [EMAIL PROTECTED] (higp1.gatelock.com.tw) ** your_document.pif Trend GateLock [EMAIL PROTECTED] (higp1.gatelock.com.tw) ** your_document.pif WORM_NETSKY.D - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) Found virus WORM_NETSKY.Z in file Notice.txt .exe (in Notice.zip) The file is deleted. - Important notice! -- Virus Warning Message (on uusnwa0p) Notice.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa08) Found virus WORM_NETSKY.Z in file Informations.txt .exe (in Informations.zip) The file is deleted. - Important informations! -- Virus Warning Message (on uusnwa08) Informations.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) Found virus WORM_NETSKY.Z in file Textfile.txt .exe (in Textfile.zip) The file is deleted. - Important textfile! -- Virus Warning Message (on uusnwa0p) Textfile.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) Found virus WORM_NETSKY.Z in file Bill.txt .exe (in Bill.zip) The file is deleted. - Important bill! -- Virus Warning Message (on uusnwa0p) Bill.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) Found virus WORM_NETSKY.Z in file Data.txt .exe (in Data.zip) The file is deleted. - Important data! -- Virus Warning Message (on uusnwa0p) Data.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) Found virus WORM_NETSKY.Z in file Bill.txt .exe (in Bill.zip) The file is deleted. - Important bill! -- Virus Warning Message (on uusnwa0p) Bill.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) Found virus WORM_NETSKY.Z in file Details.txt .exe (in Details.zip) The file is deleted. - Important details! -- Virus Warning Message (on uusnwa0p) Details.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) Found virus WORM_NETSKY.Z in file Bill.txt .exe (in Bill.zip) The file is deleted. - Important bill! -- Virus Warning Message (on uusnwa0p) Bill.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) Found virus WORM_NETSKY.Z in file Details.txt .exe (in Details.zip) The file is deleted. - Important details! -- Virus Warning Message (on uusnwa0p) Details.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) -- Found virus WORM_NETSKY.Z in file Data.txt .exe (in Data.zip) The uncleanable file is deleted. - Important data! -- Virus Warning Message (on uusnwa0p) -- Data.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) -- Found virus WORM_NETSKY.Z in file Data.txt .exe (in Data.zip) The uncleanable file is deleted. - Important data! -- Virus Warning Message (on uusnwa0p) -- Data.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) -- Found virus WORM_NETSKY.Z in file Part-2.txt .exe (in Part-2.zip) The uncleanable file is deleted. - Important! -- Virus Warning Message (on uusnwa0p) -- Part-2.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ #BJO-39658-731]: Document
Dette er en automatisk svar-epost i fra Panda Software Norge - Support. Din sak har fått nr: BJO-39658-731 Du vil motta svar på denne epost adressen når vi har fått behandlet saken. Henvis til nummeret ovenfor ved telefonhenvendelser. Ved videre henvendelser om denne saken svarer du på denne e-posten eller sender en ny mail til [EMAIL PROTECTED] med: [#BJO-39658-731] i subjekt/emne feltet. This is an automatic response from Panda Software Norway. Your case has been assigned the following number: BJO-39658-731 You will receive a reply to your question as soon as possible. Further contact regarding this matter should be done by replying to the email(s) received from us, without changing the subject field. --- Panda Software Norge - Support --- [EMAIL PROTECTED] tlf: 62 53 96 80 http://www.pandasoftware.no http://www.pandasoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ #MOV-96470-480]: Document
Dette er en automatisk svar-epost i fra Panda Software Norge - Support. Din sak har fått nr: MOV-96470-480 Du vil motta svar på denne epost adressen når vi har fått behandlet saken. Henvis til nummeret ovenfor ved telefonhenvendelser. Ved videre henvendelser om denne saken svarer du på denne e-posten eller sender en ny mail til [EMAIL PROTECTED] med: [#MOV-96470-480] i subjekt/emne feltet. This is an automatic response from Panda Software Norway. Your case has been assigned the following number: MOV-96470-480 You will receive a reply to your question as soon as possible. Further contact regarding this matter should be done by replying to the email(s) received from us, without changing the subject field. --- Panda Software Norge - Support --- [EMAIL PROTECTED] tlf: 62 53 96 80 http://www.pandasoftware.no http://www.pandasoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) -- Found virus WORM_NETSKY.Z in file Details.txt .exe (in Details.zip) The uncleanable file is deleted. - Important details! -- Virus Warning Message (on uusnwa0p) -- Details.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) -- Found virus WORM_NETSKY.Z in file Details.txt .exe (in Details.zip) The uncleanable file is deleted. - Important details! -- Virus Warning Message (on uusnwa0p) -- Details.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
-- Virus Warning Message (on uusnwa0p) -- Found virus WORM_NETSKY.Z in file Bill.txt .exe (in Bill.zip) The uncleanable file is deleted. - Important bill! -- Virus Warning Message (on uusnwa0p) -- Bill.zip is removed from here because it contains a virus. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Document
Please read the attached file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Document
Important notice! KWF Email scanner found a virus in following attachment: Notice.zip Content type: application/octet-stream Additional information from antivirus: W95/Spaces.gen Attachement has been removed by firewall.
Document
Important! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29763] - The encoding of jsp document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29763. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29763 The encoding of jsp document --- Additional Comments From [EMAIL PROTECTED] 2004-06-28 09:42 --- Jan, now I agree with you and thanks for the explanation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29763] - The encoding of jsp document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29763. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29763 The encoding of jsp document [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-06-25 19:08 --- Reverted patch. We're supposed to throw an error only if there is an encoding declaration in the XML prolog that does not match the page encoding from the page directive or jsp-config. We must not throw any error if there is no XML prolog or encoding declaration in the prolog. The motivation for this is to make sure that JSP 1.2 pages with a page directive specifying a page encoding other than the default will continue to work in JSP 2.0 in most cases. The code is currently going through lots of pains to determine whether the encoding was specified in the XML prolog, or autodetected, to decide whether an error should be thrown. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29763] - The encoding of jsp document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29763. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29763 The encoding of jsp document [EMAIL PROTECTED] changed: What|Removed |Added Priority|Other |Medium - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29763] - The encoding of jsp document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29763. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29763 The encoding of jsp document --- Additional Comments From [EMAIL PROTECTED] 2004-06-24 11:48 --- This issue blocks a issue for jsp editor in the Netbeans IDE. http://www.netbeans.org/issues/show_bug.cgi?id=43269 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29763] - The encoding of jsp document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29763. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29763 The encoding of jsp document [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-06-24 19:04 --- Fixed so that an error is reported if the page encoding specified in the page directive is different from that specified in, or autodetected from, the XML prolog of a JSP document. From your message: there are three places where the encoding for a jsp document can be set Notice that the page encoding of a JSP document is *always* derived from the XML prolog, as mandated by the XML specification. It may also be *described* in the page directive or page-encoding config element, as long as the values specified there match the value derived from the XML prolog. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29763] - The encoding of jsp document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29763. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29763 The encoding of jsp document [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2004-06-25 01:52 --- Hi Petr, I think I am going to have to revert my patch, and close this issue as not a bug instead. The reason you didn't see any error is because your JSP document did not contain any XML prolog with an explicit encoding declaration. This is to ensure backwards compatibility with JSP 1.2. Otherwise, JSP documents that used to be valid in JSP 1.2 will no longer work in JSP 2.0, which the expert group decided was unacceptable. This is why the JSP 2.0 spec says: It is a translation-time error to name different encodings in two or more of the following: the XML prolog /text declaration of a JSP document [...]. In your example, there was no explicit encoding declaration in the prolog, and therefore you should not expect to see any error. Let me know what you think. Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29763] New: - The encoding of jsp document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29763. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29763 The encoding of jsp document Summary: The encoding of jsp document Product: Tomcat 5 Version: 5.0.25 Platform: All OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi, there are three places where the encoding for a jsp document can be set. In the xml prolog according to XML 1.0 specification, deployment descriptor in the jsp-property-group and as value of pageEncoding attribute of jsp:directive.page /. When there are defined at least two of them, then they have to be the same. If there are a jsp document without xml prolog - for example: jsp:root version=1.2 xmlns:f=http://java.sun.com/jsf/core; xmlns:h=http://java.sun.com/jsf/html; xmlns:jsp=http://java.sun.com/JSP/Page; jsp:directive.page contentType=text/html/ !-- Shift_JIS -- jsp:directive.page pageEncoding=EUC-JP/ . /jsp:root the tomcat says that the encoding is UTF-8, not EUC-JP. Even when there is set the encoding EUC-JP in the deployment descriptor. If tomcat thinks that the encoding is UTF-8 it should report an error according to the JSP specification, because there is different encoding defined in value of pageEncoding. Regards Petr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 11656] - UTF-8 encoding not supported correctly in included text file or JSP Document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=11656. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=11656 UTF-8 encoding not supported correctly in included text file or JSP Document --- Additional Comments From [EMAIL PROTECTED] 2004-05-25 08:23 --- Hi, I have a similar problem with UTF-8. I explain. I have a file (index.html) with a link to a servlet in it. This file is the same on 2 servers with 1 with version 4.1.27 of Tomcat and 1 with 4.1.29. On the version 27 it work properly (URL is well encoded in UTF-8 as I wanted and in version 29 the URL is not encoded in UTF-8. I'd like to add that my servlet are the same... Any ideas on this problem ? thanks Jean - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
PATCH - jk\xdocs\jk2\configwebcom.xml - document recent status worker change
Greetings All,
The link below is a patch for the above referenced document to add in
details of the recent change to the status worker regarding style sheets.
http://normw.gknw.com/patches/configwebcom.xml.diff
The diff has been tested to display correctly in IE6 and Mozilla 1.6.
Norm
-
--- configwebcom.xml.orig 2004-04-15 18:48:43.0 +1000
+++ configwebcom.xml 2004-05-09 08:05:13.0 +1000
@@ -515,8 +515,74 @@
/p
/subsection
subsection name=status
-pWorker that outputs a page with usefull information to
monitor JK2/p
-pTo use it add a uri component assigned to this
worker/p
+pAn optional worker that outputs (HTML) pages with useful
information to monitor JK2./p
+pTo create the worker, add a [status:] or [status:'a
name'] section./p
+pThe status worker needs no 'local' name, although one
can be used if desired./p
+pTo access the worker, add a [uri] section with the
group= assigned to this worker./p
+pThe status worker has the following additional
properties:
+table
+tr
+thProperty name/th
+thDefault/th
+thDescription/th
+/tr
+tr
+tdstyleMode/td
+td0 (None)/td
+tdDefines if or how the status worker will
apply a Style Sheet to returned pages./td
+/tr
+tr
+tdstylePath/td
+tdNULL/td
+tdFor styleMode=2 or 3, where to find the
Style Sheet file./td
+/tr
+/table
+/p
+pThe syleMode setting accepts the following values:
+table
+tr
+thstyleMode value/th
+thDescription/th
+/tr
+tr
+td0/td
+tdNo Style settings are used. (Default)/td
+/tr
+tr
+td1/td
+tdUse the built-in Default Style Sheet. It is
presented as an 'Internal Style Sheet' to HTML pages./td
+/tr
+tr
+td2/td
+tdUse stylePath as a URI context to an
external Style Sheet file to be returned by the Web Server./td
+/tr
+tr
+td3/td
+tdUse stylePath as a file-system reference to
a Style Sheet file. It is presented as an 'Internal Style
+Sheet' to HTML pages./td
+/tr
+/table
+/p
+pIf the stylePath has not been set, styleMode=2 and 3 are
ignored./p
+pThe sylePath setting accepts the following values:
+table
+tr
+thstyleMode value/th
+thstylePath Description/th
+/tr
+tr
+td2/td
+tdA URI context to a file (e.g
/styles/jkstatus.css). It must begin with '/' and include the file
name./td
+/tr
+tr
+td3/td
+tdA file-system path (suitable for the OS in
use) plus file name. Also ${serverRoot}/conf/'file name'
+allows the file to be located in Apache's
conf directory./td
+/tr
+/table
+/p
+pIf the Style file cannot be found, Mode 2 records an
Apache log entry, while Mode 3 simply ignores the error./p
+pFor styleMode=2 and 3, changes in the Style Sheet are
effective on the next access to the status worker./p
/subsection
subsection name=lb
pLoadbalanced worker/p
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Document
Please read the attached file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Here is the document
Please have a look at the attached file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Here is the document
Hemos recibido su correo electrónico, en breve nos pondremos en contacto con usted. Puede ver mas informacion visite nuestra página www.refugiodegredos.com. Allí encontrará informacion de nuestro Hostal Refugio de Gredos, el Apartamento Almanzor y la Casa Rural Almanzor. Si quiere reservar, llámenos al 920 34 80 47, 650 90 18 99 Atentamente, conchi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Your document
Please have a look at the attached file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[NOD32: deleted] Re: Your document
Your document is attached. Notification from NOD32 Warning: ADESGO's Antivirus System for Linux Mail Server found the following infiltrations in this message: part000.txt - is OK your_document.pif - Win32/Netsky.D worm - unable to clean - deleted http://www.nod32.com
Re: Here is the document
Please have a look at the attached file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Your document
Please read the attached file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Antw: Re: Re: Document
Bin vom 09.04.-.18.04.2004. abwesend. Dringliches bitte zu Frau Dr. M. Prögler, Leitende Ärztin, Frauenklinik. Nicht Dringliches bearbeite ich nach meiner Rückkehr. Mit bestem Dank und freundlichen Grüssen Ch. Honegger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Stolen document
I cannot believe that. Norton AntiVirus excluído1.txt Description: plain/text - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Spam vulnerability at apache (was: Re: Photo document [TID#4977])
If I am not mistaken, this email probably results from somebody on the list having one of the many recent viruses. An email is being sent from somebody's computer, with the From or Reply-to being tomcat-dev, and the To being the Russian place. The russian site has an auto-responder, and so it sends back an email to the list.Yes, this is a mail software problem in that the russian place was automatically subscribed earlier probably from a similar virus email with a reply-to being something like tomcat-dev-subscribe at jakarta The point is that nobody necessarily has your address. But, being on such a large public list, you definitely put yourself at risk at getting more virus and spam emails. If this concerns you greatly, I'd advise getting a secondary, junk email account for posts to this list, one that you could kill someday and be done with any spam or virus mails brought to you by participation here. I myself wish I had done so. (probably too late to do much good now!) [EMAIL PROTECTED] 4/12/04 9:20:31 PM Hi, I extremely apologize for this message, but i think this needs to be figured out. I just yesterday registered my new email address with tomcat-dev, and i received the spam below almost immediately thereafter. Only a few people are aware of this email address, so the origin of spam info 99% appears to be tomcat-dev registration. Is there any chance that DNS gets resolved to one of several IPs, one of which collects these emails and uses them for spam (or perhaps is infected with a virus)? I would look for any IPs based in russia as the prime suspects, because this email contains russian text and appears to be originated there. What's worse is that 25 minutes after this spam, i received another one of similar content. Please help save me and others from this plague of the Internet. I entrusted apache.org with this address, and hope we can keep it between us. P.S. If there are other people who received similar emails, please let me, the admins, or the list know. If you let only me know, i will accumulate the number of people affected and forward this to an admin. P.P.S. I see that emails are protected in the archives publicly published, and i think this issue is in the same category. Thanks, rsa/ [EMAIL PROTECTED] wrote: russian(win-1251): ! ?? ??? ? ??? ? ? ?? ?? ?? Photo document, ??? . ??? ?? ?? . ?? ? ??, ? ??? ? [TID#4977]. ??, ? ? : [TID#4977] ? ? (subject) ??? ??? ?? ??? . ??? ? ??? ??? ?? ??? ?? (reply). C ?, ?? ??? ? ??? ?-10 http://www.m-10.ru english: Greetings, This message has been automatically generated in response to your message regarding Photo document, the content of which appears below. There is no need to reply to it now. Support has received your message and it has been assigned a ticket ID of [TID#4977]. Please include the string: [TID#4977] in the subject line of all future correspondence about this problem. To do so, you may reply to this message. WBR, Support Team Hosting Operator M-10 http://www.m-10.ru Original Message- Please, photo document. Yours sincerely +++ X-Attachment-Type: document +++ X-Attachment-Status: no virus found +++ Powered by the new F-Secure OnlineAntiVirus +++ Visit us: www.f-secure.com -Headers Follow-- Received: from [EMAIL PROTECTED] by office.m-10.ru (CommuniGate Pro GROUP 4.1.8) with GROUP id 1745058; Mon, 12 Apr 2004 17:13:05 +0400 Received: from [62.5.188.222] (HELO office.m-10.ru) by office.m-10.ru (CommuniGate Pro SMTP 4.1.8) with ESMTP id 1745042 for [EMAIL PROTECTED]; Mon, 12 Apr 2004 17:12:58 +0400 X-Antivirus: Checked by Dr.Web (http://www.drweb.net) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Photo document Date: Mon, 12 Apr 2004 17:11:48 +0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0016=_NextPart_000_0016 X-Priority: 3 X-Msmail-Priority: Normal Message-Id: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spam vulnerability at apache (was: Re: Photo document [TID#4977])
Jeff Tulley wrote: If I am not mistaken, this email probably results from somebody on the list having one of the many recent viruses. Actually, that is not necessary to see messages like this. All that needs to happen is that someone who is infected has both the email address of a subscriber and the email address of the mailing list visible (in an address book or something). The infected party does *not* have to be a subscriber himself or herself. Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spam vulnerability at apache (was: Re: Photo document [TID#4977])
Quite correct, though usually it IS the case that they are a subscriber, and that is why they have the address in their book. I personally am quite surprised that a group of individuals technical enough to participate in these forums would be falling prey to the viruses so often, so maybe you are correct and they are really non-subscribers. I HAVE noticed though a high occurrence of jakarta (tomcat _AND_ Ant) email addresses in all of the virus emails that I receive, so it seems lke they are coming from somebody on these lists. [EMAIL PROTECTED] 4/13/04 10:46:46 AM Jeff Tulley wrote: If I am not mistaken, this email probably results from somebody on the list having one of the many recent viruses. Actually, that is not necessary to see messages like this. All that needs to happen is that someone who is infected has both the email address of a subscriber and the email address of the mailing list visible (in an address book or something). The infected party does *not* have to be a subscriber himself or herself. Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spam vulnerability at apache (was: Re: Photo document [TID#4977])
Actually I have found the spam resulting from this list to be negligible. That includes the user list. On 04/13/2004 06:13 PM Jeff Tulley wrote: If I am not mistaken, this email probably results from somebody on the list having one of the many recent viruses. An email is being sent from somebody's computer, with the From or Reply-to being tomcat-dev, and the To being the Russian place. The russian site has an auto-responder, and so it sends back an email to the list.Yes, this is a mail software problem in that the russian place was automatically subscribed earlier probably from a similar virus email with a reply-to being something like tomcat-dev-subscribe at jakarta The point is that nobody necessarily has your address. But, being on such a large public list, you definitely put yourself at risk at getting more virus and spam emails. If this concerns you greatly, I'd advise getting a secondary, junk email account for posts to this list, one that you could kill someday and be done with any spam or virus mails brought to you by participation here. I myself wish I had done so. (probably too late to do much good now!) [EMAIL PROTECTED] 4/12/04 9:20:31 PM Hi, I extremely apologize for this message, but i think this needs to be figured out. I just yesterday registered my new email address with tomcat-dev, and i received the spam below almost immediately thereafter. Only a few people are aware of this email address, so the origin of spam info 99% appears to be tomcat-dev registration. Is there any chance that DNS gets resolved to one of several IPs, one of which collects these emails and uses them for spam (or perhaps is infected with a virus)? I would look for any IPs based in russia as the prime suspects, because this email contains russian text and appears to be originated there. What's worse is that 25 minutes after this spam, i received another one of similar content. Please help save me and others from this plague of the Internet. I entrusted apache.org with this address, and hope we can keep it between us. P.S. If there are other people who received similar emails, please let me, the admins, or the list know. If you let only me know, i will accumulate the number of people affected and forward this to an admin. P.P.S. I see that emails are protected in the archives publicly published, and i think this issue is in the same category. Thanks, rsa/ [EMAIL PROTECTED] wrote: russian(win-1251): ! ?? ??? ? ??? ? ? ?? ?? ?? Photo document, ??? . ??? ?? ?? . ?? ? ??, ? ??? ? [TID#4977]. ??, ? ? : [TID#4977] ? ? (subject) ??? ??? ?? ??? . ??? ? ??? ??? ?? ??? ?? (reply). C ?, ?? ??? ? ??? ?-10 http://www.m-10.ru english: Greetings, This message has been automatically generated in response to your message regarding Photo document, the content of which appears below. There is no need to reply to it now. Support has received your message and it has been assigned a ticket ID of [TID#4977]. Please include the string: [TID#4977] in the subject line of all future correspondence about this problem. To do so, you may reply to this message. WBR, Support Team Hosting Operator M-10 http://www.m-10.ru Original Message- Please, photo document. Yours sincerely +++ X-Attachment-Type: document +++ X-Attachment-Status: no virus found +++ Powered by the new F-Secure OnlineAntiVirus +++ Visit us: www.f-secure.com -Headers Follow-- Received: from [EMAIL PROTECTED] by office.m-10.ru (CommuniGate Pro GROUP 4.1.8) with GROUP id 1745058; Mon, 12 Apr 2004 17:13:05 +0400 Received: from [62.5.188.222] (HELO office.m-10.ru) by office.m-10.ru (CommuniGate Pro SMTP 4.1.8) with ESMTP id 1745042 for [EMAIL PROTECTED]; Mon, 12 Apr 2004 17:12:58 +0400 X-Antivirus: Checked by Dr.Web (http://www.drweb.net) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Photo document Date: Mon, 12 Apr 2004 17:11:48 +0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0016=_NextPart_000_0016 X-Priority: 3 X-Msmail-Priority: Normal Message-Id: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- struts 1.2 + tomcat 5.0.19 + java 1.4.2 Linux 2.4.20 Debian
Photo document [TID#4977]
russian(win-1251): ! Photo document, . . , [TID#4977]. , : [TID#4977] (subject) . (reply). C , -10 http://www.m-10.ru english: Greetings, This message has been automatically generated in response to your message regarding Photo document, the content of which appears below. There is no need to reply to it now. Support has received your message and it has been assigned a ticket ID of [TID#4977]. Please include the string: [TID#4977] in the subject line of all future correspondence about this problem. To do so, you may reply to this message. WBR, Support Team Hosting Operator M-10 http://www.m-10.ru Original Message- Please, photo document. Yours sincerely +++ X-Attachment-Type: document +++ X-Attachment-Status: no virus found +++ Powered by the new F-Secure OnlineAntiVirus +++ Visit us: www.f-secure.com -Headers Follow-- Received: from [EMAIL PROTECTED] by office.m-10.ru (CommuniGate Pro GROUP 4.1.8) with GROUP id 1745058; Mon, 12 Apr 2004 17:13:05 +0400 Received: from [62.5.188.222] (HELO office.m-10.ru) by office.m-10.ru (CommuniGate Pro SMTP 4.1.8) with ESMTP id 1745042 for [EMAIL PROTECTED]; Mon, 12 Apr 2004 17:12:58 +0400 X-Antivirus: Checked by Dr.Web (http://www.drweb.net) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Photo document Date: Mon, 12 Apr 2004 17:11:48 +0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0016=_NextPart_000_0016 X-Priority: 3 X-Msmail-Priority: Normal Message-Id: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Spam vulnerability at apache (was: Re: Photo document [TID#4977])
Hi, I extremely apologize for this message, but i think this needs to be figured out. I just yesterday registered my new email address with tomcat-dev, and i received the spam below almost immediately thereafter. Only a few people are aware of this email address, so the origin of spam info 99% appears to be tomcat-dev registration. Is there any chance that DNS gets resolved to one of several IPs, one of which collects these emails and uses them for spam (or perhaps is infected with a virus)? I would look for any IPs based in russia as the prime suspects, because this email contains russian text and appears to be originated there. What's worse is that 25 minutes after this spam, i received another one of similar content. Please help save me and others from this plague of the Internet. I entrusted apache.org with this address, and hope we can keep it between us. P.S. If there are other people who received similar emails, please let me, the admins, or the list know. If you let only me know, i will accumulate the number of people affected and forward this to an admin. P.P.S. I see that emails are protected in the archives publicly published, and i think this issue is in the same category. Thanks, rsa/ [EMAIL PROTECTED] wrote: russian(win-1251): ! Photo document, . . , [TID#4977]. , : [TID#4977] (subject) . (reply). C , -10 http://www.m-10.ru english: Greetings, This message has been automatically generated in response to your message regarding Photo document, the content of which appears below. There is no need to reply to it now. Support has received your message and it has been assigned a ticket ID of [TID#4977]. Please include the string: [TID#4977] in the subject line of all future correspondence about this problem. To do so, you may reply to this message. WBR, Support Team Hosting Operator M-10 http://www.m-10.ru Original Message- Please, photo document. Yours sincerely +++ X-Attachment-Type: document +++ X-Attachment-Status: no virus found +++ Powered by the new F-Secure OnlineAntiVirus +++ Visit us: www.f-secure.com -Headers Follow-- Received: from [EMAIL PROTECTED] by office.m-10.ru (CommuniGate Pro GROUP 4.1.8) with GROUP id 1745058; Mon, 12 Apr 2004 17:13:05 +0400 Received: from [62.5.188.222] (HELO office.m-10.ru) by office.m-10.ru (CommuniGate Pro SMTP 4.1.8) with ESMTP id 1745042 for [EMAIL PROTECTED]; Mon, 12 Apr 2004 17:12:58 +0400 X-Antivirus: Checked by Dr.Web (http://www.drweb.net) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Photo document Date: Mon, 12 Apr 2004 17:11:48 +0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0016=_NextPart_000_0016 X-Priority: 3 X-Msmail-Priority: Normal Message-Id: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
Re: Document
attachment: vkfdogaund.bmp- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-02-29 20:34 --- I have decided to not refactor the functionality (the headache was too big, for little gain). I have tested this bug, which is invalid. You are misusing something somewhere. Be it the docBase in context.xml or something else similar, I don't know, but this works fine for me. The functionality is indeed not as easy to use as it could be (but the useability enhancement is complex to achieve), but otherwise works fine. My test: /manager/deploy?config=file:/M:/test%202/META-INF/context.xmlwar=file:/M:/test%202 context.xml: Context path=/test 2 docBase=M:/test 2 debug=0 Logger className=org.apache.catalina.logger.FileLogger prefix=my_log. suffix=.txt timestamp=true/ /Context - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces --- Additional Comments From [EMAIL PROTECTED] 2004-02-27 10:48 --- No, you have to put the docBase in your context.xml (as simple copying is used, rather than saving it again, which is riskier). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces --- Additional Comments From [EMAIL PROTECTED] 2004-02-27 16:03 --- I have decided to refactor a little bit the deployer to address these issues (the check for an existing /META-INF/context.xml will be done in the deployer, which will also be in charge of saving the XML if needed). This obviously might introduce regressions, but will be cleaner. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces --- Additional Comments From [EMAIL PROTECTED] 2004-02-27 17:16 --- Remy, thanks. Will it also fix the case when deploying using the manager application? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces --- Additional Comments From [EMAIL PROTECTED] 2004-02-26 09:10 --- I read the docs: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/manager-howto.html and there's no notion about localWar option. I assume I'm not looking at the right place. So, what's the right place to look for documentation? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2004-02-26 15:26 --- I tried the deploy command with only path and war parameters, but then configuration in context.xml is not taken into account, e.g. if I define: Logger className=org.apache.catalina.logger.FileLogger directory=logs prefix=my_log. suffix=.txt timestamp=true/ in the META-INF/context.xml, then the 'with space.xml' on server does not contain the parameter. So, this is what we are trying to solve with config parameter, but unsuccessfuly - because it doesn't handle spaces correctly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces --- Additional Comments From [EMAIL PROTECTED] 2004-02-26 18:14 --- Remy, Intuitively, I would expect that if I only use the war parameter (without config and path), and my application contains META-INF/context.xml, then Tomcat should consider this context.xml file, including the 'path' attribute specified in it. Also, the docBase attribute should not be needed in this case (as it is implied by the location of context.xml), but the manager-howto.html file specifies it as mandatory. Shouldn't docBase be optional? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces --- Additional Comments From [EMAIL PROTECTED] 2004-02-26 15:38 --- Well, this is not going to be fixed, so you have to stop using config. I'll look quickly at the rest of the problem. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces --- Additional Comments From [EMAIL PROTECTED] 2004-02-26 15:19 --- Yes, bad reading. config is still harmful. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] New: - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces Summary: Problem start app with document base containing spaces Product: Tomcat 5 Version: 5.0.19 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Webapps:Manager AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have a webapp in a directory called '/local/arena/with space'. To deploy it, I issue a manager command: http://localhost:8084/manager/deploy?config=file:/local/arena/with%20space/META-INF/context.xmlwar=file:/local/arena/with%20space/ First try works, but when I restart the server, this context cannot be started and I get: org.apache.catalina.core.StandardContext resourcesStart SEVERE: Error starting static Resources java.lang.IllegalArgumentException: Document base /local/arena/with%20space does not exist or is not a readable directory org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:185) org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:3858) org.apache.catalina.core.StandardContext.start(StandardContext.java:4085) The content of Catalina/localhost/with_space.xml after deployment is: ?xml version=1.0 encoding=UTF-8? Context docBase=/local/arena/with%20space/ path=/with_space/ If I change it manually to: ?xml version=1.0 encoding=UTF-8? Context docBase=/local/arena/with space/ path=/with_space/ it starts working. See also: http://www.netbeans.org/issues/show_bug.cgi?id=40437 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces --- Additional Comments From [EMAIL PROTECTED] 2004-02-25 21:45 --- Don't use the config attribute, it will only cause trouble (Tomcat will use the one in /META-INF/context.xml fine). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27216] - Problem start app with document base containing spaces
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27216 Problem start app with document base containing spaces [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-02-25 21:47 --- Resolving the report. You should read the docs: - war is for uploading a .war file - you should use localWar instead (and config is not necessary) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 26819] New: - the charset of included document is not inherited from parent document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26819. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26819 the charset of included document is not inherited from parent document Summary: the charset of included document is not inherited from parent document Product: Tomcat 5 Version: 5.0.18 Platform: PC OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] sorry for my poor english skill when jasper parser includes document the charset of included document is not inherited from parent document so I must append %@ page language=java contentType=text/html; charset=MS949% to all my included document help me~ guru! Please, correct my problem Please, correct poor my english :) God bless U guys!! Thank you for your effort I'm always happy to play with tomcat! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 26819] - the charset of included document is not inherited from parent document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26819. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26819 the charset of included document is not inherited from parent document [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-02-10 14:26 --- This is as per the JSP specification, and is improved from TC 4.1. You can use pageEncoding, BTW, which looks a bit nicer. Kin-Man will correct me if I'm wrong. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 26819] - the charset of included document is not inherited from parent document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26819. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26819 the charset of included document is not inherited from parent document --- Additional Comments From [EMAIL PROTECTED] 2004-02-10 22:01 --- Remy is right! There are a number of changes regarding page character encoding and that file inclusion does not inherit the encoding. See JSP 2.0 spec JSP.4.1 for more detail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Internal document anchors ?
Howdy, Noticed this morning that in at least one Tomcat document: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html some internal document anchors a name= ? end with a question mark, which means any link to them will fail due to the question mark being dropped by the server. I use IE6sp1 and the links to some parts of the above document are now broken for me. Perhaps someone can attend? I think it's a bit more subtle: space followed by question mark doesn't work. A question mark preceded by a letter does work. That's why the Are there alternative ways link works. Can you confirm that? FYI, if you want other files/sections to be modified, please provided a complete and specific list of files and line numbers. Thanks, Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Internal document anchors ?
Hi, Noticed this morning that in at least one Tomcat document: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html some internal document anchors a name= ? end with a question mark, which means any link to them will fail due to the question mark being dropped by the server. I use IE6sp1 and the links to some parts of the above document are now broken for me. Perhaps someone can attend? I think it's a bit more subtle: space followed by question mark doesn't work. A question mark preceded by a letter does work. That's why the Are there alternative ways link works. Can you confirm that? yes, I can confirm this with latest Opera and IE6SP1 too... but IMO in any case a name tags should not include question marks at all since the question mark is the official separator between URL and QUERY_STRING...; and I believe the appended '#name' is still considered to be part of the URL; but regardless what is W3C or not, I think the pages should be viewable with any browser - and that means avoid '?' in name tags. Guenter. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Internal document anchors ?
Good morning Yoav from Oz, and thanks for the reply. Can confirm that my IE6sp1 does show and work with a link correctly when a non-space character is next to the (?) character, however it is my understanding that the (?) in a link is the (approved) separator between a URL and passed parameters, and hence ought to be avoided in normal links regardless. Interestingly, I saved the page locally with the idea of making a 'fixed' copy but IE6 saved the file with the space and (?) removed. Norm Howdy, Noticed this morning that in at least one Tomcat document: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html some internal document anchors a name= ? end with a question mark, which means any link to them will fail due to the question mark being dropped by the server. I use IE6sp1 and the links to some parts of the above document are now broken for me. Perhaps someone can attend? I think it's a bit more subtle: space followed by question mark doesn't work. A question mark preceded by a letter does work. That's why the Are there alternative ways link works. Can you confirm that? FYI, if you want other files/sections to be modified, please provided a complete and specific list of files and line numbers. Thanks, Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Internal document anchors ?
Howdy, OK, I've done the following to the index.xml template from which this index.html file is generated: - Removed the space before question marks, - Replaced the ? with its HTML-encoded equivalent, #63; Now these four ? links work OK for me in both IE6 and Opera. I know what you're saying regarding ? separating the request URI from the query string. As I didn't write the original page and I don't have good text to replace the current one, I didn't want to rephrase the questions that have ? at their ends ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: NormW [mailto:[EMAIL PROTECTED] Sent: Monday, January 26, 2004 3:53 PM To: Tomcat Developers List Subject: Re: Internal document anchors ? Good morning Yoav from Oz, and thanks for the reply. Can confirm that my IE6sp1 does show and work with a link correctly when a non-space character is next to the (?) character, however it is my understanding that the (?) in a link is the (approved) separator between a URL and passed parameters, and hence ought to be avoided in normal links regardless. Interestingly, I saved the page locally with the idea of making a 'fixed' copy but IE6 saved the file with the space and (?) removed. Norm Howdy, Noticed this morning that in at least one Tomcat document: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html some internal document anchors a name= ? end with a question mark, which means any link to them will fail due to the question mark being dropped by the server. I use IE6sp1 and the links to some parts of the above document are now broken for me. Perhaps someone can attend? I think it's a bit more subtle: space followed by question mark doesn't work. A question mark preceded by a letter does work. That's why the Are there alternative ways link works. Can you confirm that? FYI, if you want other files/sections to be modified, please provided a complete and specific list of files and line numbers. Thanks, Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Internal document anchors ?
Hello again and thanks for the interest... ... and the time given Tomcat. Norm - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, January 27, 2004 7:49 AM Subject: RE: Internal document anchors ? Howdy, OK, I've done the following to the index.xml template from which this index.html file is generated: - Removed the space before question marks, - Replaced the ? with its HTML-encoded equivalent, #63; Now these four ? links work OK for me in both IE6 and Opera. I know what you're saying regarding ? separating the request URI from the query string. As I didn't write the original page and I don't have good text to replace the current one, I didn't want to rephrase the questions that have ? at their ends ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: NormW [mailto:[EMAIL PROTECTED] Sent: Monday, January 26, 2004 3:53 PM To: Tomcat Developers List Subject: Re: Internal document anchors ? Good morning Yoav from Oz, and thanks for the reply. Can confirm that my IE6sp1 does show and work with a link correctly when a non-space character is next to the (?) character, however it is my understanding that the (?) in a link is the (approved) separator between a URL and passed parameters, and hence ought to be avoided in normal links regardless. Interestingly, I saved the page locally with the idea of making a 'fixed' copy but IE6 saved the file with the space and (?) removed. Norm Howdy, Noticed this morning that in at least one Tomcat document: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html some internal document anchors a name= ? end with a question mark, which means any link to them will fail due to the question mark being dropped by the server. I use IE6sp1 and the links to some parts of the above document are now broken for me. Perhaps someone can attend? I think it's a bit more subtle: space followed by question mark doesn't work. A question mark preceded by a letter does work. That's why the Are there alternative ways link works. Can you confirm that? FYI, if you want other files/sections to be modified, please provided a complete and specific list of files and line numbers. Thanks, Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Internal document anchors ?
On Mon, Jan 26, 2004 at 03:49:27PM -0500, Shapira, Yoav wrote: Howdy, OK, I've done the following to the index.xml template from which this index.html file is generated: - Removed the space before question marks, - Replaced the ? with its HTML-encoded equivalent, #63; Shouldn't these, as links, be URI encoded? With + for space and %-style unsafe characters? -- [EMAIL PROTECTED] Some people have a way with words, while others... erm... thingy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Internal document anchors ?
Good morning! Noticed this morning that in at least one Tomcat document: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html some internal document anchors a name= ? end with a question mark, which means any link to them will fail due to the question mark being dropped by the server. I use IE6sp1 and the links to some parts of the above document are now broken for me. Perhaps someone can attend? Norm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22652] - JspWriter problem? A JSP Document with contentType=text/html makes a wrong output
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22652. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22652 JspWriter problem? A JSP Document with contentType=text/html makes a wrong output [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2003-09-09 20:36 --- I have tested this with the latest TC4 and TC5 code. I had to add a /jsp:root ending tag to your example to get it to work but once I had it worked as expected. There was no extra /body tag and all the span tags were correctly located. I am therefore closing this bug report as WORKSFORME. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22439] - NPE compiling JSP Document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22439. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22439 NPE compiling JSP Document [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 22:36 --- *** Bug 22535 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22366] - UTF-16 encoding not properly processed if used in JSP document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22366. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22366 UTF-16 encoding not properly processed if used in JSP document [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-08-13 23:23 --- Apologies... this was a pilot error :-( Thanks to Kin-Man and Jan for pointing it out to me nicely :-) My web.xml needed to be nested within a jsp-config. Moreover, it is important to remove compiled classes when adjusting the web.xml in such a way, otherwise it won't impact the JSP that's already been compiled. Many thanks messieurs! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22366] New: - UTF-16 encoding not properly processed if used in JSP document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22366. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22366 UTF-16 encoding not properly processed if used in JSP document Summary: UTF-16 encoding not properly processed if used in JSP document Product: Tomcat 5 Version: 5.0.3 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Jasper2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Given the following JSP page (utf16.jsp) %@ page pageEncoding=UTF-16 contentType=text/html;charset=UTF-8 % Hello World in UTF-16! %= ALLO! % If this page is encoded in UTF-16, and the proper configuration settings are set in the deployment descriptor so the page is read with the proper encoding (must use configuration settings since UTF-16 byte values 0 to 127 do not have the same meaning as in ASCII) jsp-property-group url-patternutf16*/url-pattern page-encodingUTF-16/page-encoding /jsp-property-group the JSP page is not processed properly. The full content of the page is simply processed as template text. However if the page is in XML view, it will be processed properly: ?xml version=1.0? jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=1.2 jsp:directive.page pageEncoding=UTF-16 contentType=text/html;charset=UTF-8 / Hello World in UTF-16! jsp:expression ALLO! /jsp:expression /jsp:root - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22366] - UTF-16 encoding not properly processed if used in JSP document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22366. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22366 UTF-16 encoding not properly processed if used in JSP document --- Additional Comments From [EMAIL PROTECTED] 2003-08-13 00:36 --- What happens if you add is-xmlfalse/is-xml to your jsp-property-group? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22439] New: - NPE compiling JSP Document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22439.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22439
NPE compiling JSP Document
Summary: NPE compiling JSP Document
Product: Tomcat 5
Version: 5.0.7
Platform: Other
OS/Version: All
Status: NEW
Severity: Major
Priority: Other
Component: Jasper2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The following JSP Document doesn't compile:
!DOCTYPE html
PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3c.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html
xmlns=http://www.w3c.org/1999/xhtml;
xmlns:jsp=http://java.sun.com/JSP/Page;
xml:lang=en lang=en
jsp:directive.page contentType=text/html /
head
titleA JSP Document/title
/head
body bgcolor=white
h1All Request Parameters/h1
ul
c:forEach xmlns:c=http://java.sun.com/jsp/jstl/core;
items=${paramValues} var=current
li
${current.key}:
c:forEach items=${current.value} var=parValue
br/${parValue}
/c:forEach
/li
/c:forEach
/ul
jsp:element name=${param.element}
jsp:attribute name=style${param.style}/jsp:attribute
jsp:body${param.body}/jsp:body
/jsp:element
/body
/html
The root cause for the exception is:
java.lang.NullPointerException
org.apache.jasper.compiler.PageInfo.popPrefixMapping(PageInfo.java:339)
org.apache.jasper.compiler.JspDocumentParser.endPrefixMapping(JspDocumentParser.java:574)
org.apache.xerces.parsers.AbstractSAXParser.endNamespaceMapping(Unknown Source)
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
org.apache.xerces.impl.XMLNamespaceBinder.handleEndElement(Unknown Source)
org.apache.xerces.impl.XMLNamespaceBinder.endElement(Unknown Source)
org.apache.xerces.impl.dtd.XMLDTDValidator.endNamespaceScope(Unknown Source)
org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
Source)
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
javax.xml.parsers.SAXParser.parse(Unknown Source)
org.apache.jasper.compiler.JspDocumentParser.parse(JspDocumentParser.java:195)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:223)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:146)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:132)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:245)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:453)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:555)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:300)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:293)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
It works fine with TC 5.0.4
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22439] - NPE compiling JSP Document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22439. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22439 NPE compiling JSP Document [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-08-14 22:16 --- This is a regression from 5.0.6, and has been fixed in the head branch. To getaround it, either use 5.0.6 or the nightly build. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13587] - version out of date in some document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13587. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13587 version out of date in some document [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-06-25 01:42 --- Updated document to JSTL 1.0. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17929] New: - EL expression treated as plain text in template data attribute with Jsp Document syntax
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17929.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17929
EL expression treated as plain text in template data attribute with Jsp Document syntax
Summary: EL expression treated as plain text in template data
attribute with Jsp Document syntax
Product: Tomcat 5
Version: Nightly Build
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Other
Component: Unknown
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
When i use the xml syntax for a jsp page with Tomcat 5.0 Alpha and try to
reference an EL parameter in a template data attribute, the EL expression gets
output as plain text, i.e. it is treated as quoted plaintext within the
attribute. The behavior seems a bit strange to me, I'd expect it to output the
parameter. I've been trying to find a clarification in the JSP 2.0, and JSTL
1.0 specification but unfonrtunately no luck so far.
Example, please note that the first EL expression is treated as plain text,
while the second evaluates correctly.:
?xml version=1.0 encoding=ISO-8859-1?
jsp:root
xmlns:jsp=http://java.sun.com/JSP/Page;
xmlns:c=http://java.sun.com/jstl/core;
version=2.0
jsp:directive.page
contentType=text/html
pageEncoding=ISO-8859-1/
html
body
div class=${1+2}${1+2}/div
/body
/html
/jsp:root
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17390] - If jsp:text is provided an invalid body in the context of a JSP document, a translation error is not raised.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17390. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17390 If jsp:text is provided an invalid body in the context of a JSP document, a translation error is not raised. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
