void testToStringWithOptions() throws DcerpcException {
        dcerpcBinding.setOption("connect", "80");
        dcerpcBinding.setOption("bind", "123");
        // Order of options in toString might vary due to HashMap, so check for containment
        String result = dcerpcBinding.toString();
        assertTrue(result.startsWith(PROTO + ":" + SERVER + "[null,"), "toString should start correctly.");

<img src="/img/tutorial/security/image12.png">

## Vérifier le nom d'utilisateur { #check-the-username }

Voici un exemple plus complet.

Utilisez une dépendance pour vérifier si le nom d'utilisateur et le mot de passe sont corrects.

注意我們把 `current_user` 的型別宣告為 Pydantic 的 `User` 模型。

這能在函式內提供自動補全與型別檢查的協助。

/// tip | 提示

你可能記得，請求體也會用 Pydantic 模型宣告。

這裡因為你使用了 `Depends`，**FastAPI** 不會混淆。

///

/// check | 檢查

這個依賴系統的設計讓我們可以有不同的依賴（不同的 "dependables"），都回傳 `User` 模型。

我們不受限於只能有一個能回傳該類型資料的依賴。

///

## 其他模型 { #other-models }

現在你可以在*路徑操作函式*中直接取得目前使用者，並在**依賴注入**層處理安全機制，使用 `Depends`。

		return nil, fmt.Errorf("'%s' does not start with '%s'", rangeString, byteRangePrefix)
	}

	// Trim byte range prefix.
	byteRangeString := strings.TrimPrefix(rangeString, byteRangePrefix)

	// Check if range string contains delimiter '-', else return error. eg. "bytes=8"
	sepIndex := strings.Index(byteRangeString, "-")
	if sepIndex == -1 {
		return nil, fmt.Errorf("'%s' does not have a valid range value", rangeString)
	}

// for each op.
// TODO(srbs): We need to define `ZerosLike` here to keep the compiler happy.
// Figure out a way to avoid this.
// TODO(srbs): Should ZerosLike check-fail instead of returning nullptr?
class TapeTensor {
 public:
  explicit TapeTensor(AbstractTensorHandle* handle);
  TapeTensor(const TapeTensor& other);
  ~TapeTensor();

  int64_t GetID() const;

    //                                                                              ======
    @Override
    protected int delegateSelectCountUniquely(final ConditionBean cb) {
        // #pending check response and cast problem
        final SearchRequestBuilder builder = client.prepareSearch(asEsIndex());
        final EsAbstractConditionBean esCb = (EsAbstractConditionBean) cb;
        if (esCb.getPreference() != null) {

            // Test with concrete implementation
            assertDoesNotThrow(() -> concreteImplementation.replaceCache());
        }

        @Test
        @DisplayName("Should check if resolve hashes")
        void testIsResolveHashes() {
            // Test with mock
            when(mockReferralData.isResolveHashes()).thenReturn(true);
            assertTrue(mockReferralData.isResolveHashes());

        // Assert - type hierarchy: subclass of CIFSException and IOException
        assertTrue(ex instanceof jcifs.CIFSException, "Should extend CIFSException");
        assertTrue(ex instanceof IOException, "Should be an IOException (checked)");
    }

    @ParameterizedTest(name = "Message-only ctor preserves message: [{0}]")
    @MethodSource("messages")
    void messageConstructor_setsMessageAndNullCause(String message) {
        // Arrange & Act

                }),
        (accum, t) -> {
          /*
           * We assign these to variables before calling checkNotNull to work around a bug in our
           * nullness checker.
           */
          K key = keyFunction.apply(t);
          V newValue = valueFunction.apply(t);
          accum.put(
              checkNotNull(key, "Null key for input %s", t),

      }
    }

    /*
     * TODO(cpovirk): `return (V) removedValue` once our checker permits that.
     *
     * (We promoted a class of warnings into errors because sometimes they indicate real problems.
     * But now we need to "undo" some instance of spurious errors, as discussed in
     * https://github.com/jspecify/checker-framework/issues/8.)
     */
    return removedValue == null ? null : (V) removedValue;
  }