# 오류 처리 { #handling-errors }

API를 사용하는 클라이언트에 오류를 알려야 하는 상황은 많이 있습니다.

이 클라이언트는 프론트엔드가 있는 브라우저일 수도 있고, 다른 사람이 작성한 코드일 수도 있고, IoT 장치일 수도 있습니다.

클라이언트에 다음과 같은 내용을 알려야 할 수도 있습니다:

* 클라이언트가 해당 작업을 수행할 충분한 권한이 없습니다.
* 클라이언트가 해당 리소스에 접근할 수 없습니다.
* 클라이언트가 접근하려고 한 항목이 존재하지 않습니다.
* 등등.

이런 경우 보통 **400**번대(400에서 499) 범위의 **HTTP 상태 코드**를 반환합니다.

이는 200번대 HTTP 상태 코드(200에서 299)와 비슷합니다. "200" 상태 코드는 어떤 형태로든 요청이 "성공"했음을 의미합니다.

    * Several of these flows are appropriate for building an OAuth 2.0 authentication provider (like Google, Facebook, X (Twitter), GitHub, etc):
        * `implicit`
        * `clientCredentials`
        * `authorizationCode`
    * But there is one specific "flow" that can be perfectly used for handling authentication in the same application directly:

It streamlines the process of **building**, **deploying**, and **accessing** an API with minimal effort.

It brings the same **developer experience** of building apps with FastAPI to **deploying** them to the cloud. 🎉

FastAPI Cloud is the primary sponsor and funding provider for the *FastAPI and friends* open source projects. ✨

 * the same injector is immediately matched to this explicit binding, which means extensions
 * cannot override this binding. This is because the lookup is always short-circuited in this
 * specific situation (plain @Inject request, and plain explicit binding for the same type.)
 *
 * The simplest solution is to use a custom @Named here so it isn't bound under the plain key.

It streamlines the process of **building**, **deploying**, and **accessing** an API with minimal effort.

It brings the same **developer experience** of building apps with FastAPI to **deploying** them to the cloud. 🎉

FastAPI Cloud is the primary sponsor and funding provider for the *FastAPI and friends* open source projects. ✨

**[FastAPI Cloud](https://fastapicloud.com)** is built by the same author and team behind **FastAPI**.

It streamlines the process of **building**, **deploying**, and **accessing** an API with minimal effort.

It brings the same **developer experience** of building apps with FastAPI to **deploying** them to the cloud. 🎉

It will also take care of most of the things you would need when deploying an app, like:

* HTTPS

- [ ] Implement lease break notification handling
- [ ] Modify SmbFile to support lease-based caching
- [ ] Add lease upgrade/downgrade logic
- [ ] Implement lease epoch tracking for v2 leases

#### 1.3 Integration Points
- Modify `Smb2CreateRequest` to include lease contexts
- Update `SmbFile` caching logic to use leases
- Add lease break handling in `SmbTransport`

---

### Phase 2: Persistent Handles

            // Then
            assertNotNull(bindWithNullBinding, "Constructor should handle null binding");
            Field bindingField = DcerpcBind.class.getDeclaredField("binding");
            bindingField.setAccessible(true);
            assertNull(bindingField.get(bindWithNullBinding), "Binding should be null");
        }
    }

    @Nested
    @DisplayName("Opnum Tests")
    class OpnumTests {

- **I/O Operations** (`org.codelibs.core.io`) - File handling, resource management, stream utilities, and traversal utilities for efficient resource processing
- **Reflection** (`org.codelibs.core.lang`) - Class loading, method/field access, type introspection utilities, and generics support
- **Exception Handling** (`org.codelibs.core.exception`) - Runtime exception wrappers for common checked exceptions with consistent error handling

### Modern Java 21 Support

            // When: Parsing the binding URL
            DcerpcBinding binding = DcerpcHandle.parseBinding(url);

            // Then: Should parse correctly
            assertNotNull(binding);
            assertEquals(expectedProto, binding.getProto());
            assertEquals(expectedServer, binding.getServer());
            assertEquals(expectedEndpoint, binding.getEndpoint());
        }