> NOTE: Server side replication is supported for idempotent versions on directory objects.

### Idempotent versions on delete markers

	ttfbHist := prometheus.NewHistogramVec(
		prometheus.HistogramOpts{
			Name:    "s3_ttfb_seconds",
			Help:    "Time taken by requests served by current MinIO server instance",
			Buckets: histBuckets,
		},
		[]string{"api"},
	)
	observations := []struct {
		val   float64
		label string
	}{
		{
			val:   0.02,
			label: labels[0],
		},
		{

Dann würde es hinter den Kulissen diese JSON-kompatiblen Daten (z. B. ein `dict`) in eine `JSONResponse` einfügen, die zum Senden der <abbr title="Response – Antwort: Daten, die der Server zum anfragenden Client zurücksendet">Response</abbr> an den Client verwendet wird.

Sie können jedoch direkt eine `JSONResponse` von Ihren *Pfadoperationen* zurückgeben.

 */
package jcifs.internal;

/**
 * Container class for SMB protocol negotiation state.
 * Holds the negotiation request, response, and raw buffer data exchanged
 * between client and server during SMB protocol version negotiation.
 *
 * @author mbechler
 */
public final class SmbNegotiation {

    private final SmbNegotiationRequest request;
    private final SmbNegotiationResponse response;

      }
      repositories {
        maven configCache()
      }
    }
  }
}

projectsLoaded {
  rootProject {
    project.pluginManager.withPlugin('com.gradle.build-scan') {
      buildScan.server = 'https://gradle-enterprise.elastic.co'
    }
  }
}


final String buildCacheUrl = System.getProperty('org.elasticsearch.build.cache.url')

# Zusätzliche Statuscodes { #additional-status-codes }

Standardmäßig liefert **FastAPI** die <abbr title="Response – Antwort: Daten, die der Server zum anfragenden Client zurücksendet">Responses</abbr> als `JSONResponse` zurück und fügt den Inhalt, den Sie aus Ihrer *Pfadoperation* zurückgeben, in diese `JSONResponse` ein.

Es wird der Default-Statuscode oder derjenige verwendet, den Sie in Ihrer *Pfadoperation* festgelegt haben.

## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* Version used (`minio --version`):
* Server setup and configuration:

	URL     string      `json:"url"`
	Headers http.Header `json:"headers"`
}

// GetObjectContext provides the necessary details to perform
// download of the object, and return back the processed response
// to the server.
type GetObjectContext struct {
	OutputRoute string `json:"outputRoute"`
	OutputToken string `json:"outputToken"`
	InputS3URL  string `json:"inputS3Url"`
}

...
```

### Create your feature branch

Before making code changes, make sure you create a separate branch for these changes

```
git checkout -b my-new-feature
```

### Test MinIO server changes

After your code changes, make sure

- To add test cases for the new code. If you have questions about how to do it, please ask on our [Slack](https://slack.min.io) channel.
- To run `make verifiers`

                assertNotNull(targetInfo);
                // Should only contain server info - but might have different structure than expected
                assertTrue(targetInfo.length >= 4, "Target info should have at least terminator");
                // Check if it contains server info (implementation dependent)
                if (targetInfo.length > 4) {