From version < 89.1 >
edited by Marius Dumitru Florea
on 2017/09/27
To version < 89.2 >
edited by Vincent Massol
on 2018/04/04
< >
Change comment: Added missing viewers



Page properties
... ... @@ -1,1 +1,1 @@
1 -XWiki.mflorea
1 +XWiki.VincentMassol
... ... @@ -90,6 +90,10 @@
90 90  
91 91  Note: if the document does not exist, you will have a 404 error page, and the following parameters will not be taken into account. Use ##xpage## if you need to have the desired behavior even if the document does not exist.
92 92  
93 +* ##attachments##: Display the attachment list (e.g. ##http:~/~/
94 +* ##history##: Display the version history (e.g. ##http:~/~/
95 +* ##comments##: Display the comments (e.g. ##http:~/~/
96 +* ##information##: Display the page information (e.g. ##http:~/~/
93 93  * ##children##: {{info}}Since 7.2RC1{{/info}} display a page that lists all the children of the document. You can also add the following parameters:
94 94  ** ##hierarchy=parentchild##: do the same but display the children according to the (old) parent/child mechanism
95 95  ** ##displayHidden=true##: display the hidden documents (no matter what the user's configuration is)

The general format of XWiki URLs is ://///, where:

  • : by default it's http. It's possible to use https (See how to modify the wiki descriptor).
  • : the XWiki instance address and port, e.g. localhost:8080, In domain-mode the server also contains the subwiki name. See Accessing a wiki. In path-based mode, the server is the address of the main wiki.
  • : the name under which the XWiki web application is deployed in your Servlet Container, e.g. xwiki. See Short URLs if you wish to deploy XWiki as ROOT.
  • : the type of URL depending on the XWiki subsystem accessed. The following types are supported:
    • bin: points to a dynamic resource. Examples: an Entity to display (wiki, page, space, attachment, object, property, etc), a dynamic skin resource (image, css, js), a dynamic template resource (image, js, css, icon, etc) and more. By dynamic we mean that some computation needs to happen to compute the resource (for example some Velocity needs to be evaluated).
    • wiki: this is similar to bin but specifying the subwiki to access, in path-based mode (See Accessing a wiki).
    • rest: points to a REST Resource
    • skins: points to a static filesystem skin resource (image, js, css, etc), i.e. a resource located inside a skin directory on the filesystem.
    • resources: points to a static template resource (image, js, css, etc) on the filesystem.
    • xmlrpc: points to the now deprecated XMLRPC API (see XML-RPC Integration for more details).
    • webdav: points to a WebDAV resource (see Web DAV for more details).
  • : the path completely depends on the used. See below for more details.

If you're interested in configuring the XWiki URLs, check the URL Architecture page.

Type: bin

XWiki 7.2: Added support for Nested Spaces

There are various bin URLs. The generic format of bin URLs is bin//. The full list of is defined in the Strut Configuration file (located in WEB-INF/struts-config).

Here are some well-known actions:

  • skin: Dynamic Skin resource, e.g. http:///xwiki/bin/skin/resources/uicomponents/search/searchSuggest.css
  • jsx: Javascript Skin Extension URL, e.g. http:///xwiki/bin/jsx/AnnotationCode/Settings?language=en
  • ssx: StyleSheet Skin Extension URL, e.g. http:///xwiki/bin/ssx/AnnotationCode/Style?language=en
  • webjars: URL when accessing some resources located in a WebJar, e.g. http:///xwiki/bin/webjars/resources/path?value=requirejs%2F2.1.15%2Frequire.min.js
  • download: URL to access an attachment from a wiki page, e.g. http:///xwiki/bin/download/XWiki/JohnDoe/john.png?width=30&height=30&keepAspectRatio=true
  • view: Display Entity content (wiki, page, space, attachment, object, property, etc) with the skin applied, e.g. http:///xwiki/bin/view/Sandbox/WebHome
  • edit: Edits wiki content (page, object, property, etc), e.g. http:///xwiki/bin/edit/Sandbox/WebHome
  • get: Accessing Entity content (wiki, page, space, attachment, object, property, etc) without any skin applied, e.g. http:///xwiki/bin/get/Main/WebHome?xpage=xpart&vm=commentsinline.vm. The get action should be used to render the content of the page and nothing else (mainly used for code pages). This action is similar to the view action, but without the UI and with "text/plain" mime type set by default for the response.
  • export: Exports wiki pages to various formats (PDF, HTML, etc). See Exports.
  • viewrev: This action is the same as the view action but allowing to address a given revision of the document asked.
  • create: Provides the UI for creating new documents, e.g. http:///xwiki/bin/create/Space/NewDocument

Action: view

The additional URL paths for the view action is /...//? or /.../?


  • http:///xwiki/bin/view/Sandbox/WebHome: Views the Sandbox.WebHome page.
  • http:///xwiki/bin/view/Sandbox: Views the Sandbox.WebHome page.
  • http:///xwiki/bin/view/Space1/Space2: Views the Space1.Space2.WebHome page (if the Space2 page doesn't exist. If it exists then it views the Space1.Space2 page).
  • http:///xwiki/bin/view/Space1/Space2/: Force to always views the Space1.Space2.WebHome page (even if the Space2 page exists in the Space1 space. Note the / at the end).
  • http:///xwiki/bin/view/Space1/Space2?spaceRedirect=false: Force to always view the Space1.Space2 terminal page (even if the Space1.Space2.WebHome page exists and even if the Space1.Space2 page may not exist).

Here are some of the supported query string parameters.

Parameter: xpage

  • plain: this value indicates that only the content of the page is printed (no UI). With a document that's not using the XWiki Syntax 1.0 you can control the output syntax using outputSyntax and outputSyntaxVersion. You can also pass other parameters to allow fine-grained control:
    • raw=1: Returns the page source as is without any formatting but XML-escaped
    • raw=2: Returns the page source as is without any formatting (without any escaping)
    • htmlHeaderAndFooter=true: Since 6.3RC1 Display the HTML headers (,,, etc...) and footers (

Get Connected