Could you provide a sample jsp for your workaround?
My Faces - Dev mailing list wrote: > > > [ > https://issues.apache.org/jira/browse/TRINIDAD-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668380#action_12668380 > ] > > Jon Bullock commented on TRINIDAD-1109: > --------------------------------------- > > To quickly get round this issue I put a JSP page in front of my web app > that showed a simple text page if it detected any of the search engine > user agents. > >> Support non-standard user agents >> -------------------------------- >> >> Key: TRINIDAD-1109 >> URL: https://issues.apache.org/jira/browse/TRINIDAD-1109 >> Project: MyFaces Trinidad >> Issue Type: Bug >> Components: Skinning >> Affects Versions: 1.0.8-core, 1.2.8-core >> Environment: User agent string: Mozilla/5.0 (compatible; >> Konqueror/3.5; Linux) KHTML/3.5.9 (like Gecko) >> Reporter: Alexey Stukalov >> >> Trinidad should be able to render the request for non-supported user >> agents. >> Since 1.x.9 version, user agent's version is mandatory. >> If user agent is not recognized and its version is not set, exceptions >> are thrown: >> 1) on initial request - "version must be non-null" NPE in >> org.apache.myfaces.trinidad.context.Version._checkNonEmptyString(Version.java:197) >> 2) on subsequent requests - NPE in >> org.apache.myfaces.trinidadinternal.style.cache.FileSystemStyleCache$Key.hashCode(FileSystemStyleCache.java:1131) >> The proposed policy is to provide "default" rendering for those agent's >> that are not recognized/partially recognized (agent type or platform >> identified, but not version etc). > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > > -- View this message in context: http://www.nabble.com/-jira--Created%3A-%28TRINIDAD-1109%29-Support-non-standard-user-agents-tp17597472p23381077.html Sent from the My Faces - Dev mailing list archive at Nabble.com.
