Skip Headers
Oracle® Fusion Middleware User's Guide for Oracle Portal
11g Release 1 (11.1.1)

Part Number E10235-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

C.3 Additional Notes on Path-Based and Durable URLs

This section provides additional information about the formation of URLs in Oracle Portal. It contains the following subsections:

C.3.1 Additional Notes on the Formation of URLs in Oracle Portal

  • In URLs, page names, object names, "/portal/page/" and GUIDs are case sensitive. All other parts of the URL are not case sensitive.

  • Should users request a language for which there is no translation, an error message displays:

    The language specified in the URL is not currently supported by this Portal. (WWC-57383)
    
  • When using language codes in URLs, the codes do not stay in the path. The language gets set in the session cookie, and a redirect occurs to a new URL that does not contain the language code.

  • Users who request URLs for items for which they do not have privileges will get a message informing them that they are not authorized to view the item.

  • Oracle Portal includes the capability of providing rewrite rules for URLs. This enables you to, for example, shorten an otherwise lengthy URL or hide specific path information. You can configure this functionality on the Configure tab of page group properties. Once there, you can also access a help topic that explains this feature in more detail. See also, Section 4.5.7, "Defining URL Rewrite Rules for a Page Group".

  • All files uploaded in support of an item retain the same file name across all versions and translations of that item. When a new document file with a different file name from the other versions is uploaded (for example, for a new version of the item), then all files for all versions and translations of that same attribute (for example, the File Name attribute) will be renamed to match the new file name. This is not only true for documents, it is also true for images, Zip files, or any other file type that is uploaded in support of an item.

C.3.2 How Name, Display Name, and File Name Affect a Path-Based URL

Path-based URLs may use an item's Name, Display Name, File Name, or globally-unique identifier (GUID) to access the item. The value it uses depends on the presence and validity of these attributes.

This section sets forth a few scenarios and shows how the presence and validity of the Name, Display Name, and File Name affect how a path-based URL is formed. It contains the following subsections:

Note:

For information on the rules that govern the naming of objects in Oracle Portal, see Appendix D, "Object Naming Rules in Oracle Portal".

For information on which items are accessible in what states, see Section 17.9.3, "Item URL Security".

C.3.2.1 File-Based Item Type Has an Exposed Name Attribute

The following scenarios concern a file-based item type that has a Name attribute that is exposed through the Create and Edit Item wizards.

User supplies a valid Name, but no Display Name.

The value for the File Name attribute is displayed in the portal. The value for the Name attribute is used in the formation of the path-based URL. In this case, the value for the Name attribute would be the same as the name of the file.

User supplies a valid Name and a valid Display Name.

The value for the Display Name attribute is displayed in the portal. The value for the Name attribute is used in the formation of the path-based URL.

The File Name contains invalid characters.

The value for the Display Name attribute is displayed in the portal. If no value is supplied for the Display Name attribute, the invalid value for the File Name attribute is displayed in the portal.

The Name attribute automatically populates with the invalid file name. If the user clicks Finish without changing this value, an error is generated, and the item is not added. If the user is editing the item, and just clears the value in the Name field, the original value for the Name attribute is used in the formation of the path-based URL. By original value, we mean the value that existed before the item was edited.

If the user is adding the item, and simply clears the default value from the Name field, the item's GUID is used in the formation of the path-based URL.

C.3.2.2 File-Based Item Type Has a Hidden Name Attribute

The following scenarios concern a file-based item type that has a Name attribute that is exposed in the Create Item wizard but hidden in the Edit Item wizard. One thing to keep in mind is that, absent a user-supplied value, the Name attribute defaults to the name and extension of the file, for example, if the value in the File Name field is C:\foldername\filename.txt, the default value in the Name field is filename.txt. Wherever the Name attribute is exposed, the default value can be changed.

User adds a file-based item with a File Name that uses invalid characters. User modifies the Name to remove the invalid characters. User edits the item, where Name attribute is not exposed, adding a new file with a File Name that uses invalid characters.

The original value for the Name attribute is retained. The original value for the Name attribute is used in the formation of the path-based URL.

User adds a file-based item with a file name that uses valid characters. User edits the item, uploading a new file.

The value for the Name attribute defaults to the new value provided for the File Name attribute. The new value for the Name attribute is used in the formation of the path-based URL.

User supplies a valid Name, but no Display Name.

Where the Name attribute is present and has a value (from the Add Item wizard), it is always used in the formation of the path-based URL.

Where no value is supplied for the Name attribute, the file name is taken from the File Name attribute and used for display in the portal and in the formation of the path-based URL.

User supplies a valid Name and a valid Display Name.

Assuming the Name attribute has a value (from the Add Item wizard), the value of the Display Name attribute is displayed in the portal, and the value of the Name attribute is used in the formation of the path-based URL.

The File Name contains invalid characters.

The value of the Display Name attribute is displayed in the portal. If no value is supplied for the Display Name attribute, the invalid File Name is displayed in the portal. The value of the Name attribute is used in the formation of the path-based URL.

C.3.2.3 File-Based Item Type Has No Name Attribute

The following scenarios concern a file-based item type that does not have an associated Name attribute. For the default File item type does not have an associated Name attribute, just File Name and Display Name attributes.

User provides a valid value for the Display Name attribute.

The value for the Display Name attribute is displayed in the portal. The file name is taken from the value of the File Name attribute and used in the formation of the path-based URL.

User does not supply a Display Name.

The file name is taken from the value of the File Name attribute and displayed in the portal as well as used in the formation of the path-based URL.

File name has invalid characters.

The value of the Display Name attribute is displayed in the portal if present. If not present, the invalid File Name is displayed in the portal. The invalid characters are stripped from the File Name to form the internal name, which is used in the formation of the path-based URL.

C.3.3 The Language Parameter in Path-Based and Durable URLs

The following list provides the values you can use for the lang parameter in path-based and durable URLs:

  • Arabic: …/lang-ar/…

  • Brazilian Portuguese: …/lang-pt-BR/…

  • Canadian French: …/lang-fr-CA/…

  • Chinese (Simplified): …/lang-zh-CN/…

  • Chinese (Traditional): …/lang-zh-TW/…

  • Czech: …/lang-cs/…

  • Danish: …/lang-da/…

  • Dutch: …/lang-nl/…

  • English: …/lang-en/…

  • Finnish: …/lang-fi/…

  • French: …/lang-fr/…

  • German: …/lang-de/…

  • Greek: …/lang-el/…

  • Hebrew: …/lang-iw/…

  • Hungarian: …/lang-hu/…

  • Italian: …/lang-it/…

  • Japanese: …/lang-ja/…

  • Korean: …/lang-ko/…

  • Latin American Spanish: …/lang-es/…

  • Norwegian: …/lang-no/…

  • Polish: …/lang-pl/…

  • Portuguese: …/lang-pt/…

  • Romanian: …/lang-ro/…

  • Russian: …/lang-ru/…

  • Slovak: …/lang-sk/…

  • Spanish: …/lang-es/…

  • Swedish: …/lang-sv/…

  • Thai: …/lang-th/…

  • Turkish: …/lang-tr/…