In some special use cases (probably not very common), you might want to **restrict** the headers that you want to receive.

You can use Pydantic's model configuration to `forbid` any `extra` fields:

{* ../../docs_src/header_param_models/tutorial002_an_py310.py hl[10] *}

If a client tries to send some **extra headers**, they will receive an **error** response.

			if len(gotFields) != len(test.expectedFields) {
				t.Errorf("Expected keys %d, found %d", len(test.expectedFields), len(gotFields))
			}
			found := true
			for _, field := range gotFields {
				_, ok := test.expectedFields[field]
				found = found && ok
			}
			if !found {
				t.Errorf("Expected %s, got %s", test.expectedFields, gotFields)
			}
		})
	}
}

func TestValidRegion(t *testing.T) {

                                    </la:info>
                                    <la:errors/>
                                </div>
                                    <%-- Form Fields --%>
                                <table class="table table-bordered" aria-label="<la:message key="labels.bad_word_details" />">
                                    <tbody>
                                    <tr>

            this.parsed = true;
        }

        boolean isParsed() {
            return parsed;
        }
    }

    @Test
    @DisplayName("Default state is null for both fields")
    void defaultStateIsNull() {
        TestSpnegoToken t = new TestSpnegoToken();
        assertNull(t.getMechanismToken(), "mechanismToken should default to null");

				}
			}

			for _, name := range []string{f.DBName, f.Name} {
				if name != "" {
					if field := s.LookUpField(name); field == nil || (field.Name != name && field.DBName != name) {
						t.Errorf("schema %v failed to look up field with dbname %v", s, f.DBName)
					}
				}
			}

			if f.PrimaryKey {
				var found bool

        jcifs.SID[] in = new jcifs.SID[] { s1, s2 };

        // Stub sendrecv to emulate successful RPC response
        doAnswer(inv -> {
            // Capture the outgoing RPC and populate result fields as the server would
            Object msg = inv.getArgument(0);
            assertTrue(msg instanceof jcifs.dcerpc.msrpc.MsrpcLookupSids);

        ComponentUtil.getRelatedContentHelper().update();
    }

    /**
     * Sets up the search conditions for listing related content entities.
     * Configures wildcard searches for term and content fields, and sets up ordering.
     *
     * @param cb the condition bean for building the query
     * @param relatedContentPager the pager containing search parameters
     */

        verify(mockDcerpcHandle).sendrecv(rpcCaptor.capture());
        MsrpcSamrOpenAlias capturedRpc = rpcCaptor.getValue();
        // We cannot directly access private fields of MsrpcSamrOpenAlias or its superclass
        // Instead, we verify the interaction with the DcerpcHandle and the return value.
        // The fact that the constructor completes without exception and sets 'opened' to true

You can use Pydantic's model configuration to `forbid` any `extra` fields:

{* ../../docs_src/cookie_param_models/tutorial002_an_py310.py hl[10] *}

If a client tries to send some **extra cookies**, they will receive an **error** response.

        "colorMode": "value",
        "graphMode": "area",
        "justifyMode": "auto",
        "orientation": "auto",
        "reduceOptions": {
          "calcs": [
            "mean"
          ],
          "fields": "",
          "values": false
        },
        "showPercentChange": false,
        "text": {},
        "textMode": "auto",
        "wideLayout": true
      },
      "pluginVersion": "10.4.0",