-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when API sets a cookie #12
Comments
Thank you for the error report, can you please post your hookfiles and I should have some time to dig into this tonight. |
Here is the more complete detailed error it gives:
Will post hookfiles in a sec. |
I was able to replicate the issue with an example setup. Here is the example: https://github.com/grounded042/goodman-set-cookie. I did not add any hooks to show that it happens without writing any hooks but just by compiling the hooks and running |
@grounded042 so I am able to reproduce the issue and also am pretty confident I know why it is occurring. This line here will create a header like so
Since goodman uses RPC to execute the hooks, the transactions are encoded / decoded via the gob package. It seems to be that when the above header structure is mixed with key value pairs like I think the solution is to treat header values always like I am gonna be away this weekend but I will try to resolve this issue as soon as I can. |
Sweet! Thanks for taking a look. |
@grounded042 a little update, I am struggling to reproduce this in a testing environment because I am trying to add a new cucumber / aruba test and since I am not a ruby guy I am having problems writing the test. Hoping to have something updated this week however. |
Whenever my API responds with a header
Set-Cookie
, I get the errorinfo: Hook handler stderr: panic: RPC client threw error gob: type not registered for interface: []interface {}
I have narrowed this down to the
Set-Cookie
header. If I name the header anything else, it doesn't give me that error, but when I name itSet-Cookie
I always get that error.The text was updated successfully, but these errors were encountered: