Attempting to create a file space that already exists
File spaces that you create through the WebSphere® MQ File Transfer Edition Web Gateway must have unique names. If you attempt to create a file space with a name that is already in use, this will be treated as an attempt to modify the file space. If you do not have permission to modify the file space, you receive an HTTP error code and a WebSphere MQ File Transfer Edition error message.
- This HTTP request submits a request to create a file space called murray.
In this example, the file space murray already exists
and the user submitting the request does not have permission to modify
this file space.
POST HTTP/1.1 /admin/filespace/murray Host: example.com User-Agent: mozilla Content-Type: application/xml Content-Length: 266 <?xml version="1.0" encoding="UTF-8"?> <filespaces> <filespace> <quota bytes="1048576"/> <writers> <authorized> <agent-user>neerav</agent-user> <agent-user>SYS.ADMIN.*</agent-user> </authorized> <unauthorized> <agent-user>olivia</agent-user> </unauthorized> </writers> </filespace> </filespaces>
- The Web Gateway returns an HTTP response with the following format:
HTTP/1.1 400 Bad Request Server: Apache-Coyote/1.1 Content-Type: text/plain;charset=ISO-8859-1 BFGWI0014E: User not authorized to perform the request.
To make the request valid, specify a file space name that is not already in use. For information about listing the file spaces in your WebSphere MQ File Transfer Edition environment, see the topics Example: Listing all file spaces and Web Gateway administration API reference.
For more information about the error codes returned by the Web Gateway administration API, see the HTTP Response Codes topic.