Customizing Web-viewable URL Used In FileStoreProvider Configurations Causes 403 Forbidden Errors (Doc ID 2775032.1)

Last updated on DECEMBER 18, 2023

Applies to:

Goal

What FileStoreProvider configurations are needed to create a web-viewable URL that stores a sub-set of content in a unique folder structure when accessing Content Information page for a content item?

Example:
Web Location: http://<WCC_HostName>:16200/cs/groups/public/documents/manuals/Test123.pdf
To
Web Location: http://<WCC_HostName>:16200/cs/groups/public/<CustomFolder>/documents/manuals/Test123.pdf

When making changes to a new file storage rule, followed by server restart, following error occurs:
Error 403--Forbidden

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.4 403 Forbidden

The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable. 

Test Case:
1. Created a custom storage rule (File system only with "Is Webless file store" option not selected) and added a custom directory to the WebViewable, Vault and Web URL File paths as noted below.
========================================================
    Vault Path:
    $#env.VaultDir$<CustomFolder>/$dDocType$/$dDocAccount$/$dispersion$/$dID$$ExtensionSeparator$$dExtension$

    Web-viewable Path:
    $FsWeblayoutDir$groups/$dSecurityGroup$/<CustomFolder>/$dDocAccount$/documents/$dDocType$/$dispersion$/$endDispMarker$/$dDocName$$RenditionSpecifier$$RevisionLabel$$ExtensionSeparator$$dWebExtension$

    Web URL File Path:
    $FsHttpWebRoot$groups/$dSecurityGroup$/<CustomFolder>/$dDocAccount$/documents/$dDocType$/$dispersion$/$endDispMarker$/$dDocName$$RenditionSpecifier$$RevisionLabel$$ExtensionSeparator$$dWebExtension$
========================================================
2. Uploaded a content item to be stored thru the new storage rule.
3. Navigated to the Doc Info page for above content item.
4. Clicked on the Web Location link on the Doc Info page.
5. Above referenced 403 error is encountered.

Actual Result: Error 403 is experienced.
Expected Result: User should be directed to Web-viewable copy of the content item.

Conclusion: Failed to add custom directory in the FileStoreProvider configuration.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.