Bug 31922 – umc-client: Support for mime type application/octet-stream

Bug 31922 - umc-client: Support for mime type application/octet-stream


Summary:	umc-client: Support for mime type application/octet-stream

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 3.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 3.x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-07-09 09:44 CEST by Stefan Gohmann
Modified:	2016-10-07 18:08 CEST (History)
CC List:	2 users (show)

See Also:	31923
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Gohmann

2013-07-09 09:44:27 CEST

Needed for Bug #26785.

UMC does not support the mime type application/octet-stream, for example:

root@master501:~# umc-command -U Administrator -P univention upload/schema -F share.schema -m application/octet-stream -o name=share.schema
Usage: umc-command [options] command <arguments>

umc-command: error: option -m: invalid choice: 'application/octet-stream' (choose from 'application/json', 'image/jpeg', 'image/png')
root@master501:~#

Comment 1 Florian Best

2013-07-10 17:04:38 CEST

When the patch from Bug #31923 is applied this does not need to be done.
Every uploaded file has it's own mimetype field but the request mimetype still keeps being JSON.

UMCP is not designed to support mutliple request mimetypes. The mimetype should always be application/json. UMCP-Messages with an other mimetype than JSON does not support Flavor, Message, Result, Status and Options as these are information stored in the Message body instead of the UMCP-Protocol headers.

Comment 2 Florian Best

2016-10-07 18:08:41 CEST

Use univention.lib.umc_connection (or the cli-client from toolshed) for this.