import org.codelibs.fess.util.ComponentUtil;
import org.lastaflute.web.response.next.HtmlNext;
import org.lastaflute.web.util.LaRequestUtil;

/**
 * Helper class for managing virtual host configurations and routing.
 * This class provides functionality to handle virtual host-based routing
 * and path resolution based on HTTP headers.
 */
public class VirtualHostHelper {

    /**
     * Default constructor.

        // search

    }

    /**
     * Retrieves all request headers associated with a specific web configuration.
     *
     * @param webConfigId the unique identifier of the web configuration
     * @return a list of request headers associated with the specified web configuration
     */
    public List<RequestHeader> getRequestHeaderList(final String webConfigId) {

        assertEquals(testWindowSize, queryRescorerBuilder.windowSize().intValue());
    }

    public void test_evaluate_multipleCallsWithDifferentConfigs() {
        // Test multiple calls with different configurations
        Map<String, Object> params = new HashMap<>();
        params.put("param", "value");

        // First call with model name
        ComponentUtil.setFessConfig(new FessConfig.SimpleImpl() {

The <abbr title="specification">spec</abbr> requires the fields to be exactly named `username` and `password`, and to be sent as form fields, not JSON.

With `Form` you can declare the same configurations as with `Body` (and `Query`, `Path`, `Cookie`), including validation, examples, an alias (e.g. `user-name` instead of `username`), etc.

/// info

`Form` is a class that inherits directly from `Body`.

///

 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package configurations

import common.Os
import common.applyDefaultSettings
import jetbrains.buildServer.configs.kotlin.ParameterDisplay
import jetbrains.buildServer.configs.kotlin.ReuseBuilds
import model.CIBuildModel

These functions are there (instead of just using the classes directly) so that your editor doesn't mark errors about their types.

That way you can use your normal editor and coding tools without having to add custom configurations to disregard those errors.

package configurations

import common.BuildToolBuildJvm
import common.Jvm
import common.Os
import common.buildScanTagParam
import common.buildToolGradleParameters
import common.customGradle
import common.functionalTestParameters
import common.getBuildScanCustomValueParam
import common.gradleWrapper
import common.requiresNotEc2Agent
import common.requiresNotSharedHost
import common.skipConditionally

href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers" class="external-link" target="_blank">using the 'X-' prefix</a>.

But if you have custom headers that you want a client in a browser to be able to see, you need to add them to your CORS configurations ([CORS (Cross-Origin Resource Sharing)](cors.md){.internal-link target=_blank}) using the parameter `expose_headers` documented in <a href="https://www.starlette.io/middleware/#corsmiddleware" class="external-link" target="_blank">Starlette's...

package configurations

import common.Arch
import common.BuildToolBuildJvm
import common.Jvm
import common.KillProcessMode.KILL_ALL_GRADLE_PROCESSES
import common.KillProcessMode.KILL_LEAKED_PROCESSES_FROM_PREVIOUS_BUILDS
import common.KillProcessMode.KILL_PROCESSES_STARTED_BY_GRADLE
import common.Os
import common.VersionedSettingsBranch
import common.applyDefaultSettings
import common.buildScanTagParam
import common.buildToolGradleParameters

        // this configuration is on fess_env.properties because this is true only when development
        direction.directDevelopmentHere(fessConfig.isDevelopmentHere());

        // titles of the application for logging are from configurations
        direction.directLoggingTitle(fessConfig.getDomainTitle(), fessConfig.getEnvironmentTitle());