-
Notifications
You must be signed in to change notification settings - Fork 20
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
Arquillian URL injection #26
Comments
johnament
added a commit
to johnament/arquillian-extension-rest
that referenced
this issue
Sep 7, 2016
…, not HTTPContext. Fixed shrinkwrap version.
johnament
added a commit
to johnament/arquillian-extension-rest
that referenced
this issue
Sep 7, 2016
…, not HTTPContext. Fixed shrinkwrap version.
johnament
added a commit
to johnament/arquillian-extension-rest
that referenced
this issue
Sep 7, 2016
…, not HTTPContext. Fixed shrinkwrap version.
This should be good in the next release. I've refactored the code to leverage the returned value of URL injection, instead of manually looking it up. The injection of URL didn't exist when this extension was first created (at least not injection in a non-client form) |
johnament
added a commit
to johnament/arquillian-extension-rest
that referenced
this issue
Sep 7, 2016
…, not HTTPContext. Fixed shrinkwrap version.
johnament
added a commit
to johnament/arquillian-extension-rest
that referenced
this issue
Sep 7, 2016
…, not HTTPContext. Fixed shrinkwrap version.
johnament
added a commit
to johnament/arquillian-extension-rest
that referenced
this issue
Sep 7, 2016
…, not HTTPContext. Fixed shrinkwrap version.
johnament
added a commit
to johnament/arquillian-extension-rest
that referenced
this issue
Jan 6, 2018
…, not HTTPContext. Fixed shrinkwrap version.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I config the container section on arquillian.xml specifing a different host:port on the protocol attribute and the host:port is in another machine different from localhost, arquillian rest continues using the rest endpoint as localhost, making the request to have zero response.
The text was updated successfully, but these errors were encountered: