description: |
        How has this issue affected you? What are you trying to accomplish? What other alternatives have you considered?
        Providing context helps us come up with a solution that is most useful in the real world
    validations:

      label: Context (optional)
      description: |
        How has this issue affected you? What are you trying to accomplish?
        Providing context helps us come up with a solution that is most useful in the real world
    validations:
      required: false
  - type: input
    id: page
    attributes:
      label: Page with the problem
      description: Please, provide a link to the relevant documentation page
    validations:

import org.junit.jupiter.api.extension.RegisterExtension

class CompressionInterceptorTest {
  @RegisterExtension
  val clientTestRule = OkHttpClientTestRule()

  val source =
    Buffer().apply {
      write("Hello World".encodeUtf8())
    } as Source

  @Test
  fun emptyDoesntChangeRequestOrResponse() {
    val empty = CompressionInterceptor()
    val client =
      clientTestRule
        .newClientBuilder()

/**
 * Result of a project build call.
 *
 * @since 4.0.0
 */
@Experimental
public interface ProjectBuilderResult extends Result<ProjectBuilderRequest> {

    /**
     * Gets the identifier of the project that could not be built. The general format of the identifier is {@code
     * <groupId>:<artifactId>:<version>} but some of these coordinates may still be unknown at the point the exception

./mc replicate add sitea/bucket --remote-bucket siteb/bucket

# Run the test to make sure proxying of DEL marker doesn't happen
loop_count=0
while true; do
	if [ $loop_count -eq 1000 ]; then
		break
	fi
	echo "Hello World" | ./mc pipe sitea/bucket/obj$loop_count
	./mc rm sitea/bucket/obj$loop_count
	RESULT=$({ ./mc stat --no-list sitea/bucket/obj$loop_count; } 2>&1)
	if [[ ${RESULT} != *"Object does not exist"* ]]; then

      label: Context (optional)
      description: |
        How has this issue affected you? What are you trying to accomplish?
        Providing context helps us come up with a solution that is most useful in the real world
    validations:
      required: false
  - type: textarea
    id: steps-to-reproduce
    attributes:
      label: Self-contained Reproducer Project
      description: |

    }

    @Test
    @DisplayName("Should join two elements with delimiter")
    void testJoinTwoElements() {
        String result = StringUtil.join(",", "hello", "world");
        assertEquals("hello,world", result);
    }

    @Test
    @DisplayName("Should join multiple elements with delimiter")
    void testJoinMultipleElements() {

    void testRefactoredEncryptionDecryption() throws Exception {
        // Given - Use same key for both encryption and decryption in test
        // In production, client would use clientEncKey/serverDecKey and server would use serverEncKey/clientDecKey
        Smb2EncryptionContext context = new Smb2EncryptionContext(EncryptionNegotiateContext.CIPHER_AES128_GCM, DialectVersion.SMB311,

                SmbConstants.DEFAULT_SHARING);

        byte[] data = "Hello World".getBytes();

        // When
        outputStream.write(data, 6, 5); // Write "World"

        // Then
        verify(mockTreeHandle, atLeastOnce()).send(any(Smb2WriteRequest.class), any());
    }

    @Test

Console target is on always and cannot be disabled.

### Logging HTTP Target

HTTP target logs to a generic HTTP endpoint in JSON format and is not enabled by default. To enable HTTP target logging you would have to update your MinIO server configuration using `mc admin config set` command.

Assuming `mc` is already [configured](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart)

```