Skip to main content

me_core

parse_rust_server::routes::sessions

Function me_core 

Source 
pub async fn me_core(
    state: &AppState,
    rc: &RequestContext,
) -> Result<Value, ParseError>
Expand description

GET /sessions/me (SessionsRouter.js:12-61).

Three messages, and none of them is /users/me’s. A missing token is Session token required.; a token that resolves to nothing at either step is Session token not found. GET /users/me answers Invalid session token for both, and a client matching on the string would see the difference.

The two-step shape is upstream’s and is not redundant: the row is located with master so the token can be validated at all, then re-fetched by objectId with the caller’s own auth so that protected fields and CLP apply to what comes back.