* application/e-pub+zip=epub<br>
     * application/x-ibooks+zip=ibooks<br>
     * text/plain=txt<br>
     * application/rtf=rtf<br>
     * application/vnd.ms-htmlhelp=chm<br>
     * application/zip=zip<br>
     * application/x-7z-comressed=7z<br>
     * application/x-bzip=bz<br>
     * application/x-bzip2=bz2<br>
     * application/x-tar=tar<br>
     * application/x-rar-compressed=rar<br>

  ) {
  }

  /**
   * Invoked when data from the response body is first available to the application.
   *
   * This is typically invoked immediately before bytes are returned to the application. If the
   * response body is empty this is invoked immediately before returning that to the application.
   *
   * If the application closes the response body before attempting a read, this is invoked at the
   * time it is closed.
   *

    <<online>> status, or else doesn't care.

  * Otherwise, don't bind the mojo. Log a debug message to indicate that it is
    sensitive the online state of the application, and that this state is
    currently wrong for execution.

    <<NOTE:>> Do we want to fail when we cannot bind a mojo to the lifecycle
    because of offline/online status? That would probably indicate that the user

class ResponseLevel0(JSONResponse):
    media_type = "application/x-level-0"


class ResponseLevel1(JSONResponse):
    media_type = "application/x-level-1"


class ResponseLevel2(JSONResponse):
    media_type = "application/x-level-2"


class ResponseLevel3(JSONResponse):
    media_type = "application/x-level-3"


class ResponseLevel4(JSONResponse):
    media_type = "application/x-level-4"

                            "description": "Successful Response",
                            "content": {"application/json": {"schema": {}}},
                        },
                        "422": {
                            "description": "Validation Error",
                            "content": {
                                "application/json": {
                                    "schema": {

        assertContentType("application/msword", "test/text1.txt", "hoge.doc");
        assertContentType("application/msword", "extractor/msoffice/test.doc", "hoge.doc");
        assertContentType("application/vnd.ms-excel", "test/text1.txt", "hoge.xls");
        assertContentType("application/vnd.ms-excel", "extractor/msoffice/test.xls", "hoge.xls");
        assertContentType("application/vnd.ms-powerpoint", "test/text1.txt", "hoge.ppt");

			<arg>"application/vnd.ms-excel.sheet.3"</arg>
		</postConstruct>
		<postConstruct name="addCondition">
			<arg>"mimetype"</arg>
			<arg>"application/vnd.ms-excel.sheet.4"</arg>
		</postConstruct>
		<postConstruct name="addCondition">
			<arg>"mimetype"</arg>
			<arg>"application/vnd.ms-excel.workspace.3"</arg>
		</postConstruct>
		<postConstruct name="addCondition">
			<arg>"mimetype"</arg>

application/mac-binhex40       hqx              # Macintosh binhexed archives
application/mspowerpoint       ppt              # Microsoft Powerpoint
application/msword             doc              # Microsoft Word
application/octet-stream       bin exe ani      # Binary File
application/oda                oda
application/pagemaker          pm5 pt5 pm       # PageMaker
application/pdf                pdf              # Adobe Acrobat

                                "content": {"application/json": {"schema": {}}},
                            },
                            "422": {
                                "description": "Validation Error",
                                "content": {
                                    "application/json": {
                                        "schema": {

  - liveness/readiness probes to kube-scheduler MUST use HTTPS now, and the default port has been changed to 10259.