Novell Home

My Favorites

Close

Please to see your favorites.

Vibe users unable to see newly created folders in the sidebar when using Safari 6 browser

This document (7010807) is provided subject to the disclaimer at the end of this document.

Environment

Novell Vibe 3.3

Situation

If you try to create a folder in Vibe using Safari 6 browser, you may not immediately see that folder show up in the Vibe sidebar. A hard refresh will show you that the folder was in fact created. The same may occur when creating or modifying entries. As a result, users are led to believe that their changes were lost and never saved.

Resolution

By making a small change in the web.xml file for Vibe, we can force the browser to never cache the results.

Follow these steps to update your current Vibe installation:

NOTE: This fix is intended for Vibe 3.3 and will be overwritten if the Vibe 3.3 installer is re-run in Update Software mode. 

1. Stop the Vibe service (Linux: /etc/init.d/teaming stop)

2. Make a backup of the following file in your Vibe install:
    <TEAMING INSTALL>/apache-tomcat/webapps/ssf/WEB-INF/web.xml such as web.xml.original33

3. Modify the original <TEAMING INSTALL>/apache-tomcat/webapps/ssf/WEB-INF/web.xml file as follows:

    a.  Look for the following section in the web.xml file:
         <filter-mapping>
             <filter-name>publicResourcesFilter</filter-name>
             <url-pattern>/static/*</url-pattern>
         </filter-mapping>

    b. Add the following section just before the section specified above in step 3a:
         <filter-mapping>
             <filter-name>privateResourcesFilter</filter-name>
             <url-pattern>*.rpc</url-pattern>
         </filter-mapping>

4. Save your changes to the <TEAMING INSTALL>/apache-tomcat/webapps/ssf/WEB-INF/web.xml file

5. (Important) Make certain the file permissions and ownership on the modified web.xml file is exactly the same as the one you backed up

6. Start the Vibe service (Linux: /etc/init.d/teaming start)

Cause

Safari 6 caches the response from POST (for all GWT RPC requests) rather than resending the request.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7010807
  • Creation Date:20-SEP-12
  • Modified Date:20-SEP-12
    • NovellVibe

Did this document solve your problem? Provide Feedback