RestAssured not configured to use the correct port when quarkus.http.test-ssl-port is set
#20228
Labels
Milestone
Comments
jamesnetherton
changed the title
quarkus.http.test-ssl-port is setquarkus.http.test-ssl-port is set
|
/cc @geoand |
|
Is this still an issue? I vaguely remember us addressing something similar |
|
Issue still seems to be present in Quarkus 2.16.0.Final. |
|
Interesting, thanks for the update |
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Jan 27, 2023
Also change the port from which the secure connection is established from `quarkus.https.test-port` to `quarkus.http.test-ssl-port` - Fixes quarkusio#20228
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When a custom value for
quarkus.http.test-ssl-portis set, RestAssured seems to not be configured to use it. Digging into the code, it appears that it's actually attempting to be set by resolving config propertyquarkus.https.test-port.https://github.com/quarkusio/quarkus/blob/main/test-framework/common/src/main/java/io/quarkus/test/common/RestAssuredURLManager.java#L118-L120
There's also a couple of other references to it in the codebase:
https://github.com/quarkusio/quarkus/search?q=%22quarkus.https.test-port%22
Expected behavior
The RestAssured port is configured to use the value of
quarkus.http.test-ssl-port.Actual behavior
RestAssured.portevaluates to8444and not the value ofquarkus.http.test-ssl-port.How to Reproduce?
Create a unit test where
quarkus.http.test-ssl-portis configured. Then use RestAssured to try and hit a server endpoint.Output of
uname -aorverNo response
Output of
java -versionNo response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: