Skip to content
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.

Sign up for GitHub

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

Jump to bottom

proxyaddr ignored #36

Closed
y-luis-rojo opened this issue Jul 25, 2018 · 1 comment · Fixed by #46
Closed

proxyaddr ignored #36

y-luis-rojo opened this issue Jul 25, 2018 · 1 comment · Fixed by #46
Labels
bug

Comments

@y-luis-rojo
Copy link
Contributor

When dirpath and proxyaddr are set, the last is ignored because of its indentation.
@y-luis-rojo
Copy link
Contributor Author

Created PR #35

@goodboy goodboy mentioned this issue Oct 12, 2018
Open
goodboy pushed a commit that referenced this issue Oct 12, 2018
Add test for #36
760b9bd 
Add a test which demonstrates a bug where if a scenario is loaded from
a directory that the `proxyaddr` is never set.
goodboy pushed a commit that referenced this issue Oct 12, 2018
Fix #36
685735f 
Thanks to @y-luis for originally finding and fixing this problem.
The original PR (#35) was discarded accidentally.
@goodboy goodboy mentioned this issue Oct 12, 2018
Merged
@goodboy goodboy added the bug label Jun 10, 2019
goodboy pushed a commit that referenced this issue Jul 4, 2019
@goodboy
Add test for #36
9099998 
Add a test which demonstrates a bug where if a scenario is loaded from
a directory that the `proxyaddr` is never set.
goodboy pushed a commit that referenced this issue Jul 4, 2019
@goodboy
Fix #36
16bca29 
Thanks to @y-luis for originally finding and fixing this problem.
The original PR (#35) was discarded accidentally.
goodboy pushed a commit that referenced this issue Jul 4, 2019
@goodboy
Add test for #36
1adf41f 
Add a test which demonstrates a bug where if a scenario is loaded from
a directory that the `proxyaddr` is never set.
goodboy pushed a commit that referenced this issue Jul 4, 2019
@goodboy
Fix #36
79b7534 
Thanks to @y-luis for originally finding and fixing this problem.
The original PR (#35) was discarded accidentally.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Proxyaddr fix SIPp/pysipp
2 participants
@goodboy @y-luis-rojo