DOCSLIB.ORG

K9660: Configuring the BIG-IP Webaccelerator to Recognize Icalendar Files

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
K9660: Configuring the BIG-IP Webaccelerator to Recognize Icalendar Files K9660: Configuring the BIG-IP WebAccelerator to recognize iCalendar files Non-Diagnostic Original Publication Date: Jan 29, 2009 Update Date: Jul 3, 2018 Topic The BIG-IP WebAccelerator does not have an object type in the /config/wa/globalfragment.xml file to support iCalendar files often used by Apple iCal, Google Calendar, Mozilla Sunbird, and other calendar programs. These files usually have an .ics or .ifb extension and are labeled with the text/calendar MIME media type. F5 Networks Product Development is tracking a request for enhancement to add this functionality as CR113103. Workaround To add an object type for iCalendar files to the globalframent.xml file and configure an acceleration policy to use the new object type, perform the following two procedures: Adding a documents.ical object type for iCalendar files to the globalfragment.xml file Configuring an acceleration policy with an iCal documents node that uses the documents.ical object type Adding a documents.ical object type for iCalendar files to the globalfragment.xml file To add a documents.ical object type for iCalendar files to the globalfragment.xml file, perform the following procedure: 1. Log in to the command line. 2. Change directories to the /config/wa directory by typing the following command: cd /config/wa 3. Back up the original globalfragment.xml file by typing the following command: cp globalfragment.xml globalfragment.xml.sol9660 4. Open the globalfragment.xml file in a text editor. 5. Add the following objType entry to the end of the objTypes section: <objType type="ical" group="documents" category="common" 5. displayName="iCalendar" ext="ics,ifb,ical" mimeType=" text/calendar" compressToClient="policyControlled" /> 6. Save the globalfragment.xml file. 7. Restart the pvac daemon by typing the following command: Important: Restarting the pvac daemon will briefly disrupt connections, and invalidate objects in the LTM RAM Cache. Restarting the pvac daemon should be scheduled accordingly. bigstart restart pvac The documents.ical file can now be used for the Content Type in the Matching Rules section of a WebAccelerator policy. Configuring an acceleration policy with an iCal documents node that uses the documents.ical object type To configure an acceleration policy with an iCal documents node that uses the documents.ical object type, perform the following procedure: Note: Pre-defined Acceleration policies are not modifiable; this procedure must be performed on a User- defined Acceleration policy. 1. Log in to the BIG-IP WebAccelerator Configuration utility. 2. Click WebAccelerator. 3. Click Policies. A new Policies Configuration window opens. 4. Click on the User-defined Acceleration policy to be configured. 5. Click the plus ( + ) sign to expand the Site nodes. 6. Click the plus sign to expand the Static nodes. 7. Click the plus sign to expand the Documents nodes. 8. Click on the Misc Client Uncompr. node. 9. Click the Copy link at the top of the policy tree. 10. Type iCal in the Name field. 11. Click the Copy button. 12. Click on the new iCal node. 13. Select Matching Rules from the drop-down menu. 14. Click Content Type. 15. Delete the contents of the Value matches text field. 16. Type documents.ical in the Value matches text field. 17. Click the Save button. 18. Click the Publish button. 19. Optionally, type a comment or note in the Comment field. 20. Click the Publish Now button. Applies to: Product: BIG-IP, BIG-IP WebAccelerator 10.0.1, 10.0.0, 9.4.8, 9.4.7, 9.4.6, 9.4.5, 9.4.4, 9.4.3, 9.4.2, 9.4.1, 9.4.0.
Load more

Recommended publications
  • Architecture of the World Wide Web, First Edition Editor's Draft 14 October 2004
    Architecture of the World Wide Web, First Edition Editor's Draft 14 October 2004 This version: http://www.w3.org/2001/tag/2004/webarch-20041014/ Latest editor's draft: http://www.w3.org/2001/tag/webarch/ Previous version: http://www.w3.org/2001/tag/2004/webarch-20040928/ Latest TR version: http://www.w3.org/TR/webarch/ Editors: Ian Jacobs, W3C Norman Walsh, Sun Microsystems, Inc. Authors: See acknowledgments (§8, pg. 42). Copyright © 2002-2004 W3C ® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements. Abstract The World Wide Web is an information space of interrelated resources. This information space is the basis of, and is shared by, a number of information systems. In each of these systems, people and software retrieve, create, display, analyze, relate, and reason about resources. The World Wide Web uses relatively simple technologies with sufficient scalability, efficiency and utility that they have resulted in a remarkable information space of interrelated resources, growing across languages, cultures, and media. In an effort to preserve these properties of the information space as the technologies evolve, this architecture document discusses the core design components of the Web. They are identification of resources, representation of resource state, and the protocols that support the interaction between agents and resources in the space. We relate core design components, constraints, and good practices to the principles and properties they support. Status of this document This section describes the status of this document at the time of its publication.
    [Show full text]
  • WS-Calendar Version 1.0
    1 2 WS-Calendar Version 1.0 3 Working Draft 04 4 20100509 5 Specification URIs: 6 This Version: 7 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-04.pdf 8 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-04.html 9 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-04.doc 10 Previous Version: 11 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-03.pdf 12 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-03.html 13 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-03.doc 14 Latest Version: 15 http://docs.oasis-open.org/ws-calendar/v1.0/ws-calendar-1.0-spec.pdf 16 http://docs.oasis-open.org/ws-calendar/v1.0/ws-calendar-1.0-spec.html 17 http://docs.oasis-open.org/ws-calendar/v1.0/ws-calendar-1.0-spec.doc 18 Technical Committee: 19 OASIS WS-Calendar TC 20 Chair(s): 21 Toby Considine 22 23 Editor(s): 24 Toby Considine 25 Paul Tischhauser 26 27 Related work: 28 This specification replaces or supersedes: 29 N/A 30 This specification is related to: 31 IETF RFC 5545, ICalendar 32 IETF RFC 5546, ICalendar Transport 33 IETF RFC 2447, ICalendar Message Based Interoperability 34 IETF XCal in process 35 36 Declared XML Namespace(s): 37 http://docs.oasis-open.org/ns/ws-calendar/ws-calendar-201001 38 Abstract: 39 WS-Calendar describes a common set of message components for specifying schedules and intervals to 40 coordinate activities between services.
    [Show full text]
  • Supplement 211: Dicomweb Support for the Application/Zip Payload
    5 Digital Imaging and Communications in Medicine (DICOM) Supplement 211: 10 DICOMweb Support for the application/zip Payload 15 20 Prepared by: Bill Wallace, Brad Genereaux DICOM Standards Committee, Working Group 27 1300 N. 17th Street Rosslyn, Virginia 22209 USA 25 Developed in accordance with work item WI 2018 -09 -C VERSION: 19 January 16, 2020 Table of Contents Scope and Field of Application ........................................................................................................................................ iii 30 Open Questions ....................................................................................................................................................... iii Closed Questions .................................................................................................................................................... iiii 8.6.1.3.1 File Extensions ................................................................................................................................. viv 8.6.1.3.2 BulkData URI ................................................................................................................................... viv 8.6.1.3.3 Logical Format ........................................................................................................................................ viv 35 8.6.1.3.4 Metadata Representations ...................................................................................................................... viv Scope and Field of Application
    [Show full text]
  • Fast and Scalable Pattern Mining for Media-Type Focused Crawling
    Provided by the author(s) and NUI Galway in accordance with publisher policies. Please cite the published version when available. Title Fast and Scalable Pattern Mining for Media-Type Focused Crawling Author(s) Umbrich, Jürgen; Karnstedt, Marcel; Harth, Andreas Publication Date 2009 Jürgen Umbrich, Marcel Karnstedt, Andreas Harth "Fast and Publication Scalable Pattern Mining for Media-Type Focused Crawling", Information KDML 2009: Knowledge Discovery, Data Mining, and Machine Learning, in conjunction with LWA 2009, 2009. Item record http://hdl.handle.net/10379/1121 Downloaded 2021-09-27T17:53:57Z Some rights reserved. For more information, please see the item record link above. Fast and Scalable Pattern Mining for Media-Type Focused Crawling∗ [experience paper] Jurgen¨ Umbrich and Marcel Karnstedt and Andreas Harthy Digital Enterprise Research Institute (DERI) National University of Ireland, Galway, Ireland fi[email protected] Abstract 1999]) wants to infer the topic of a target page before de- voting bandwidth to download it. Further, a page’s content Search engines targeting content other than hy- may be hidden in images. pertext documents require a crawler that discov- ers resources identifying files of certain media types. Na¨ıve crawling approaches do not guaran- A crawler for media type targeted search engines is fo- tee a sufficient supply of new URIs (Uniform Re- cused on the document formats (such as audio and video) source Identifiers) to visit; effective and scalable instead of the topic covered by the documents. For a scal- mechanisms for discovering and crawling tar- able media type focused crawler it is absolutely essential geted resources are needed.
    [Show full text]
  • Describing Media Content of Binary Data in XML W3C Working Group Note 4 May 2005
    Table of Contents Describing Media Content of Binary Data in XML W3C Working Group Note 4 May 2005 This version: http://www.w3.org/TR/2005/NOTE-xml-media-types-20050504 Latest version: http://www.w3.org/TR/xml-media-types Previous version: http://www.w3.org/TR/2005/NOTE-xml-media-types-20050502 Editors: Anish Karmarkar, Oracle Ümit Yalç&#305;nalp, SAP Copyright © 2005 W3C ® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. > >Abstract This document addresses the need to indicate the content-type associated with binary element content in an XML document and the need to specify, in XML Schema, the expected content-type(s) associated with binary element content. It is expected that the additional information about the content-type will be used for optimizing the handling of binary data that is part of a Web services message. Status of this Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/. This document is a W3C Working Group Note. This document includes the resolution of the comments received on the Last Call Working Draft previously published. The comments on this document and their resolution can be found in the Web Services Description Working Group’s issues list. There is no technical difference between this document and the 2 May 2005 version; the acknowledgement section has been updated to thank external contributors.
    [Show full text]
  • 2016 Technical Guidelines for Digitizing Cultural Heritage Materials
    September 2016 Technical Guidelines for Digitizing Cultural Heritage Materials Creation of Raster Image Files i Document Information Title Editor Technical Guidelines for Digitizing Cultural Heritage Materials: Thomas Rieger Creation of Raster Image Files Document Type Technical Guidelines Publication Date September 2016 Source Documents Title Editors Technical Guidelines for Digitizing Cultural Heritage Materials: Don Williams and Michael Creation of Raster Image Master Files Stelmach http://www.digitizationguidelines.gov/guidelines/FADGI_Still_Image- Tech_Guidelines_2010-08-24.pdf Document Type Technical Guidelines Publication Date August 2010 Title Author s Technical Guidelines for Digitizing Archival Records for Electronic Steven Puglia, Jeffrey Reed, and Access: Creation of Production Master Files – Raster Images Erin Rhodes http://www.archives.gov/preservation/technical/guidelines.pdf U.S. National Archives and Records Administration Document Type Technical Guidelines Publication Date June 2004 This work is available for worldwide use and reuse under CC0 1.0 Universal. ii Table of Contents INTRODUCTION ........................................................................................................................................... 7 SCOPE .......................................................................................................................................................... 7 THE FADGI STAR SYSTEM .......................................................................................................................
    [Show full text]
  • Scheduling Standards Resources
    Memorandum To: Oasis-Open LegalXML ECF TC From: James McMillan, National Center for State Courts Re: Scheduling standards resources Per request from the TC, I have prepared the following resource list from our discussion with the experts from the CalConnect, The Calendaring and Scheduling Consortium: http://www.calconnect.org/ Pertinent to our efforts is that this group is participating in the OASIS-Open Web Services Calendar group (WS-Calendar) TC https://www.oasis-open.org/apps/org/workgroup/ws-calendar/ And one of the ideas that the expert group suggested is that ECF send a representative to the upcoming CalConnect XXXII conference scheduled for San Jose, CA, January 26-30, 2015 (http://www.calconnect.org/calconnect32.shtml ). Also please note that as part of the conference they hold their their CalConnect Interoperability Test Event: http://www.calconnect.org/iop1501.shtml Standards The following are a list of scheduling and calendar related standards that the experts recommended that ECF study and consider for guidance for our possible scheduling extension. iCalendar (http://en.wikipedia.org/wiki/ICalendar ) is a computer file format which allows Internet users to send meeting requests and tasks to other Internet users, via email, or sharing files with an extension of .ics. Recipients of the iCalendar data file (with supporting software, such as an email client or calendar application) can respond to the sender easily or counter- propose another meeting date/time. There is an excellent properties chart shown here for the standard: http://en.wikipedia.org/wiki/ICalendar#mediaviewer/File:ICalendarSpecification.png iTip Standard (https://www.ietf.org/rfc/rfc2446.txt )- defines a protocol for exchanging iCalendar objects for the purposes of group calendaring and scheduling between "Calendar Users" (CUs); whoever initiates the exchange of data takes on the role of the "Organizer".
    [Show full text]
  • Media Type Application/Vnd.Oracle.Resource+Json
    New Media Type for Oracle REST Services to Support Specialized Resource Types O R A C L E WHITEPAPER | M A R C H 2 0 1 5 Disclaimer The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Contents Introduction 3 Conventions and Terminology 3 Core terminology 3 Singular Resource 4 Collection Resource 8 Exception Detail Resource 13 Status Resource 14 Query Description Resource 15 create-form Resource 16 edit-form Resource 17 JSON Schema 18 IANA Considerations 28 References 28 Change Log 28 2 | ORACLE WHITEPAPER: NEW MEDIA TYPE FOR ORACLE REST SERVICES TO SUPPORT SPECIALIZED RESOURCE TYPES Introduction This document defines a new media type, application/vnd.oracle.resource+json, which can be used by REST services to support the specialized resource types defined in the following table. Resource Type Description Singular Single entity resource, such as an employee or a purchase order. For more information, see “Singular Resource.” Collection List of items, such as employees or purchase orders. See “Collection Resource.” Exception Detail Detailed information about a failed request. See “Exception Detail Resource.” Status Status of a long running job. See “Status Resource.” Query description Query syntax description used by client to build the "q" query parameter.
    [Show full text]
  • Social Media Solution Guide
    Social Media Solution Guide Deploy Social Messaging Server with an RSS Channel 9/30/2021 Deploy Social Messaging Server with an RSS Channel Deploy Social Messaging Server with an RSS Channel Contents • 1 Deploy Social Messaging Server with an RSS Channel • 1.1 Prepare the RSS Channel • 1.2 Configure the Options • 1.3 Interaction Attributes • 1.4 Next Steps Social Media Solution Guide 2 Deploy Social Messaging Server with an RSS Channel Warning The APIs and other features of social media sites may change with little warning. The information provided on this page was correct at the time of publication (22 February 2013). For an RSS channel, you need two installation packages: Social Messaging Server and Genesys Driver for Use with RSS. The Driver adds RSS-specific features to Social Messaging Server and does not require its own Application object in the Configuration Server database. You can also create a Custom Media Channel Driver. Important Unlike some other eServices components, Social Messaging Server does not require Java Environment and Libraries for eServices and UCS. Prepare the RSS Channel 1. Deploy Social Messaging Server. 2. Run the installation for Genesys Driver for Use with RSS, selecting the desired Social Messaging Server object: Social Media Solution Guide 3 Deploy Social Messaging Server with an RSS Channel Select your Social Messaging Server Object 3. Locate the driver-for-rss-options.cfg configuration file in the \<Social Messaging Server application>\media-channel-drivers\channel-rss directory. 4. In Configuration Manager, open your Social Messaging Server Application, go to the Options tab, and import driver-for-rss-options.cfg.
    [Show full text]
  • Wrangling Messy CSV Files by Detecting Row and Type Patterns
    Wrangling Messy CSV Files by Detecting Row and Type Patterns Gerrit J.J. van den Burg1, Alfredo Nazábal1, and Charles Sutton1,2,3 1The Alan Turing Institute, London, UK 2Google, Inc. Mountain View, CA, USA 3School of Informatics, The University of Edinburgh, UK November 29, 2018 Abstract It is well known that data scientists spend the majority of their time on preparing data for analysis. One of the first steps in this preparation phase is to load the data from the raw storage format. Comma-separated value (CSV) files are a popular format for tabular data due to their simplicity and ostensible ease of use. However, formatting standards for CSV files are not followed consistently, so each file requires manual inspection and potentially repair before the data can be loaded, an enormous waste of human effort for a task that should be one of the simplest parts of data science. The first and most essential step in retrieving data from CSV files is deciding on the dialect of the file, such as the cell delimiter and quote character. Existing dialect detection approaches are few and non-robust. In this paper, we propose a dialect detection method based on a novel measure of data consistency of parsed data files. Our method achieves 97% overall accuracy on a large corpus of real- world CSV files and improves the accuracy on messy CSV files by almost 22% compared to existing approaches, including those in the Python standard library. Keywords — Data Wrangling, Data Parsing, Comma Separated Values arXiv:1811.11242v1 [cs.DB] 27 Nov 2018 1 CSV is a textbook example of how not to design a textual file format.
    [Show full text]
  • Reference Guide
    Reference Guide Mulberry Internet Email and Calendar Client Version 4.0 Cyrus Daboo mailto:[email protected] Pittsburgh PA http://www.mulberrymail.com USA 2Information in this document is subject to change without notice. You are free to use this document in any way you wish provided full attribution of the original author is given. Document Revision 405.000 © 2006 Cyrus Daboo. All Rights Reserved. Pittsburgh PA USA Mulberry is a registered trademark. All other companies and product names are trademarks or registered trademarks of their respective holders. Contents 1. INTRODUCTION................................................................................. 15 2. GETTING STARTED............................................................................ 16 2.1 SYSTEM REQUIREMENTS .......................................................................................................... 16 2.2 INSTALLING MULBERRY........................................................................................................... 17 2.3 GETTING HELP......................................................................................................................... 18 2.4 STARTING MULBERRY .............................................................................................................. 18 2.5 DRAG AND DROP ...................................................................................................................... 20 2.6 CONTEXTUAL MENUS.............................................................................................................
    [Show full text]
  • Client-Side Web Technologies
    Client-Side Web Technologies Introduction to HTTP MIME • Multipurpose Internet Mail Extensions • Introduced in 1996 • Created to extend email to http://www.maran.com/dictionary/m/mime/image.gif support: • Text in character sets other than ASCII • Non-text content • Multi-part message Bodies • Header info in non-ASCII character sets MIME Header Fields • MIME-Version • Declares version of message Body format standard in use • Content-Type • DescriBes the data contained in the Body • Content-Disposition • DescriBes how a Body part should Be presented (e.g. inline or attachment) • There are others But we won’t discuss them… MIME Content-Type • DescriBes the data in the Body of a MIME entity • Consists of: • Top level media type • Declares the general type of data • SuBtype • Specifies a specific format for that type of data • Parameters that modify the suBtype (optional) • Due to expanded use, now known as Internet Media Types • IANA maintains the list of registered Media Types: • http://www.iana.org/assignments/media-types Top-Level Media Types • Text • Textual information • Image • Image data • Audio • Audio data • Video • Video data • Application • Some other kind of data (typically Binary, to Be processed By some application) • Multipart • Data consisting of multiple entities of independent data types • SuBtypes such as mixed, alternative, byteranges, and form-data (for HTML forms) MIME Message Examples From: John Doe <[email protected]> Subject: Hello MIME-Version: 1.0 Content-Type: text/plain; This is a message in MIME format. From:
    [Show full text]