Replies: 1 comment
-
I'm getting the cookie out of the request now, so I have a workaround. But I'd rather make a special 'robot cookie'. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Perhaps a wrongheaded move, but I'm interested in creating a cookie string that I can send to a remote service. That remote service would use it to make requests from the server.
This would be the same string I get if I log in from the remote using username and password, and on the server make a token and put it into the session. Its something like this:
id=5JUJQDbcva7QKEnQBKz9ghwh9uKS%2FjqtSJGBdVU4dHym+r7o3dsRls8Pvmc6WbAy6O1lANxbrmSuHNUh2FbnPnLhbGk6Qatfz+GQa+a4%2FEY%3D; HttpOnly; SameSite=Lax; Path=/; Max-Age=31449600
Since I don't know the user's password though (just the hash of the pwd), I can't send it to the remote. I'd rather just send the cookie text anyway.
What I can't figure out is how to make sure a string (the cookie "id") using actix-extras. Is this being prevented by design? Its not obvious how to do it.
Beta Was this translation helpful? Give feedback.
All reactions