Show last authors
1 1 URLs resolution
3 In a single instance of XWiki you have many sections and the URLs need to reflect all that. This documentation details the way URLs are parsed by XWiki and what means each part of it.
7 1.1 Protocol
8 By default "http" is used when generating an url in XWiki. You can set "secure" parameter to true in a wiki descriptor to generate urls with "https" in "http".
10 1.1 Host
11 * The first thing XWiki do to find the right wiki the URL is pointing to is by trying to find <tt></tt> in the list of wiki descriptors.
12 * I no descriptor can be found:
13 ** if the host is an IP (,, etc.) XWiki goes to main wiki
14 ** if the first part of the host name (what is before the first point) is "www" XWiki goes to main wiki
15 ** if the first part of the host name match a wiki identifier XWiki goes to this wiki
17 1.1 \[OPTIONNAL\] Application context
18 #warning("TODO")
20 1.1 \[OPTIONNAL\]/bin/
21 #warning("TODO")
24 1.1 \[OPTIONNAL\] Action
25 XWiki use "action" identifiers to determine what is the goal a the user when going to a page.
27 For example if the action is "edit" XWiki will print a editor the user use to modify a page content but if the "view" action is used XWiki will execute the page content to print/render the content.
29 1.1 Space
30 All XWiki page are located in what is called a "space". You have only one level of space but you can indicate a "parent space" for a space.
32 1.1 Page
33 The page is what contains wiki contents and objects/classes and attachments.
35 1.1 Attachment
36 This part indicate the attachment you want to download from a particular page.
38 1.1 Parameters
39 Actions can use URL parameters to modify there action depending of there value.
41 For example you can make a velocity script that print the content of this value with:
42 {code}
43 The value of the parameter is: $request.param1
44 {code}
45 if you have a parameter "param1=Hello World" the result will be
46 {code}
47 The value of the parameter is: Hello World
48 {code}

Get Connected