leptos-server-fn

Leptos server functions return 500 errors when inputs or outputs lack Serialize + Deserialize bounds, or when async futures violate Send boundaries. Correct encoding selection and proper extractor usage prevent these runtime failures.

You use Axum extractors within Leptos server functions by leveraging the context for response manipulation. The function must enforce Send bounds across async boundaries and apply correct encoding to ensure reliable data extraction.

Use Leptos server functions when you need seamless type-safe client-server calls with automatic serialization. Choose plain Axum handlers when you need standard HTTP routing without enforcing Serialize + Deserialize bounds or Send requirements.

Encoding selection for Leptos server functions depends on your data transfer requirements. You must enforce Serialize for inputs and Deserialize for outputs to ensure correct data transmission and prevent processing errors.

You manipulate HTTP responses from Leptos server functions by accessing and modifying the response via the function's context. This allows response shaping while maintaining required Send bounds across async boundaries.

Yes, Leptos server functions require Send bounds across async boundaries to work reliably. Futures must be Send by design to prevent runtime issues and 500 errors during concurrent server execution.