// by AWS S3.
//
// An AWS S3 ETag is 16 bytes long and, in case of a multipart
// upload, has a `-N` suffix encoding the number of object parts.
// An ETag is not AWS S3 compatible when encrypted. When sending
// an ETag back to an S3 client it has to be formatted to be
// AWS S3 compatible.
//
// Therefore, Format returns the last 16 bytes of an encrypted
// ETag.
//

        final EventInfo event = new EventInfo();
        event.name = "config_updated";
        event.data = "web_config";
        event.instanceId = "sender@host1";
        coordinatorHelper.dispatchEvent(event);

        assertEquals("web_config", receivedData.get());
        assertEquals("sender@host1", receivedInstanceId.get());
    }

    // ===================================================================================

            return;
        }
        final Smb2NegotiateRequest negoReq = new Smb2NegotiateRequest(sess.getConfig(), trans.getRequestSecurityMode(nego));

        log.debug("Sending VALIDATE_NEGOTIATE_INFO");
        final Smb2IoctlRequest req = new Smb2IoctlRequest(sess.getConfig(), Smb2IoctlRequest.FSCTL_VALIDATE_NEGOTIATE_INFO);
        req.setFlags(Smb2IoctlRequest.SMB2_O_IOCTL_IS_FSCTL);

			writeErrorResponseJSON(ctx, w, apiErr, r.URL)
			return
		}
	}

	// Check if we are creating svc account for request sender.
	isSvcAccForRequestor := targetUser == requestorUser || targetUser == requestorParentUser

	// If we are creating svc account for request sender, ensure
	// that targetUser is a real user (i.e. not derived
	// credentials).
	if isSvcAccForRequestor {
		if requestorIsDerivedCredential {

        });
    }

    /**
     * Sends a test mail using the provided notification settings.
     *
     * @param form the mail form containing notification settings
     * @return HTML response after sending test mail
     */
    @Execute
    @Secured({ ROLE })
    public HtmlResponse sendmail(final MailForm form) {
        validate(form, messages -> {}, () -> asHtml(path_AdminGeneral_AdminGeneralJsp));

    }

    /**
     * Bind event handlers
     */
    function bindEvents() {
        elements.sendBtn.on('click', sendMessage);

        elements.chatInput.on('keydown', function(e) {
            // Prevent sending during IME composition (Japanese, Chinese, etc.)
            if (e.key === 'Enter' && !e.shiftKey && !e.isComposing) {
                e.preventDefault();
                sendMessage();
            }
        });

you had a client that was sending an invalid Content-Type or Accept header to
the API, in 1.2 you will either receive a 415 or 406 error.
The only client
this is known to affect is curl when you use -d with JSON but don't set a
content type, helpfully sends "application/x-www-urlencoded", which is not
correct.
Other client authors should double check that you are sending proper

## 2. Protocol Specification Reference

- **MS-SMB2 Section 3.2.4.23**: FSCTL_QUERY_NETWORK_INTERFACE_INFO
- **MS-SMB2 Section 3.2.5.14.8**: Sending an SMB2 IOCTL Request for FSCTL_QUERY_NETWORK_INTERFACE_INFO
- **MS-SMB2 Section 3.1.5.3**: Receiving an SMB_COM_NEGOTIATE
- **MS-SMB2 Section 3.2.4.1.6**: Alternative Channel Creation

For applications still sending queries to GSA endpoints, Fess provides a configuration option:

**Enable GSA API**

Add to `system.properties`:
```properties
web.api.gsa=true
```

            } else {
                setLMResponse(new byte[24]);
            }

            if (avPairs != null) {
                // make sure to set the TARGET_INFO flag as we are sending
                setFlag(NtlmFlags.NTLMSSP_NEGOTIATE_TARGET_INFO, true);
            }

            final byte[] responseKeyNT = NtlmUtil.nTOWFv2(domain, user, passwordHash);