2020

Table Of Contents
USING QUARKXPRESS SERVER
Dissecting a QXP Server URL
To interact with QuarkXPress Server from a Web browser, use a URL like the
following:
http://[server]:[port]/[namespace]/[directory]/[DocumentName]?[pa
rameter]=Value
[server]: The name or IP address of the computer for QuarkXPress Server or
QuarkXPress Server Manager.
[port]: The port number on which to contact QuarkXPress Server or
QuarkXPress Server Manager. The default port is 8080 for QuarkXPress Server
and 8090 for QuarkXPress Server Manager.
[namespace]: Defines what the URL action will be and any parameters and
conditions available to that namespace.
[directory]: The path in the document pool where the project is stored,
relative to the QuarkXPress Server document pool. To access the root level, no
directory path is necessary. (Note that you can also supply assets as part of a
multipart HTTP request. For more information, see “Using HTTP POST with QXP
Server.”)
[DocumentName]: The name of the QuarkXPress project to be processed.
[parameter]: Further defines the URL action with attributes and values allowed
for the namespace or general call. Pass parameters in the form
attribute=value, with parameters separated by the “&” character.
For QuarkXPress Server Manager, use a URL like the following:
http://[server]:[port]/qxpsm/request/[namespace]/[directory]/
[DocumentName]?[parameter]=Value
Prior to QuarkXPress Server 9.0, you had to use different URL constructions when
sending requests to an instance of QuarkXPress Server Manager in a QPS installation
than you did when sending requests to a free-standing instance of QuarkXPress
Server Manager. In versions 9.0 and later, both can use /qxpsm/request/ after
[port]/ .
You can now use both absolute and relative paths when you modify a project with
SDK objects or classes. Relative paths are almost always relative to the document
pool. If you use multiple QuarkXPress Server instances, you should use a common
document pool.
Interpreting the QXP Server Manager response
When QuarkXPress Server Manager successfully processes a request through the
HTTP interface, the response is the same as QuarkXPress Server’s response unless the
user has supplied additional parameters to QuarkXPress Manager. For more
information, see “Working with QuarkXPress Server Manager” in A Guide to
QuarkXPress Server.
If an error occurs, QuarkXPress Server Manager retries the request, either on the
same QuarkXPress server instance or a different one (depending on the error and
global settings established in the QuarkXPress Server Manager client). If
QuarkXPress Server Manager cannot process the request, it returns an XML response
A GUIDE TO QUARKXPRESS SERVER 2020 | 33