Cannot extract values of any keys sent, but only on some platforms

[jr1221]

Hi,
I am trying to extract an auth string upon a client connection.

I have tried both req_parts and TryData and I always get the key just fine in the header map. This works great when on my development machine both in release and debug builds.

However only when deploying on our prod linux machine do I find that the value of the map is blank. Always blank. The client is sending the same payload, but the recieved payload only includes the header key. Here is a sample of my extracting:

io.ns(
        "/",
        |socket: SocketRef, TryData(auth): TryData<FxHashMap<String, String>>| async move {
            // unfortunate locking and ref counting due to the async closures
            // format should be map with string nerpass as key and value as client id starting with v1-
            let mut owned = writable_socket_map.write().await;
            let client_id = match auth {
                Ok(auth) => match auth.get("nerpass") {
                    Some(id) => id.clone(),
                    None => {
                        warn!("Could not find nerpass in auth, client unauthenticated");
                        return;
                    }
                },
                Err(e) => {
                    warn!("Could not extract auth, client unauthenticated: {}", e);
                    return;
                }
            };

            debug!(
                "Establishing auth connection with {} -- socket {}",
                client_id, socket.id
            );
            owned.insert(client_id.clone(), socket.id);
            drop(owned);

            socket.on_disconnect(async move || {
                writable_socket_map.write().await.remove(&client_id);
            });
        },
    );

I have an altnerate version with req_parts that exhibits the same issue. Occassionally on prod the string will get through -- but only once. I am really stumped here, any ideas as to what I may be doing wrong are much appreciated.

[Totodore]

Hey, could you publish a minimal reproducible example? There might be a race condition or something like that.

[jr1221]

Ah sorry I forgot to close this. The problem involved the caching of the connection such that I only sent my header the 2nd time I tried to connect, but by then it was a reconnection and the header was cached. It seems tk be client side.