TudbuT/conduit
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

send home_server on login response again

Browse source 
a 6+ year old deprecated field that isnt even spelled
right, and no clients use it must still be sent
according to spec

Signed-off-by: strawberry <strawberry@puppygock.gay>
This commit is contained in:
strawberry 2024-01-24 12:15:23 -05:00 • committed by June
parent 9d1ca3e84a
commit 6c1358d0c8
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
src/api/client_server/session.rs
View file

@ -184,7 +184,7 @@ pub async fn login_route(body: Ruma<login::v3::Request>) -> Result<login::v3::Re
info!("{} logged in", user_id); info!("{} logged in", user_id);
// home_server is deprecated but ruma skips serialising if None, so this is fine // home_server is deprecated but apparently must still be sent despite it being deprecated over 6 years ago.
// initially i thought this macro was unnecessary, but ruma uses this same macro for the same reason so... // initially i thought this macro was unnecessary, but ruma uses this same macro for the same reason so...
#[allow(deprecated)] #[allow(deprecated)]
Ok(login::v3::Response { Ok(login::v3::Response {
@ -199,7 +199,7 @@ pub async fn login_route(body: Ruma<login::v3::Request>) -> Result<login::v3::Re
} }
}, },
expires_in: None, expires_in: None,
home_server: None, home_server: Some(services().globals.server_name().to_owned()),
refresh_token: None, refresh_token: None,
}) })
} }