search

rbeckman-nextgen / test-mc6

0 stars 0 forks source link

Administrator Launcher does not work if we define a http context path #4232

Closed rbeckman-nextgen closed 4 years ago

rbeckman-nextgen commented 4 years ago

https://github.com/nextgenhealthcare/connect/issues/5

{quote}If the variable http.contextpath (in mirth.properties) is defined other than root, the administrator launcher fails to connect with the error "Unable to retrieve payload from HTTP request. URI: https://10.33.25.176:9443/webstart".

As can be seen in this message, the context does not appear. So it seems that one step of the connection attempt removes it.{quote}

Imported Issue. Original Details: Jira Issue Key: MIRTH-4380 Reporter: narupley Created: 2019-01-29T07:59:00.000-0800

rbeckman-nextgen commented 4 years ago

We have this same issue, we define a context path and when we launch the jnlp via the admin laucher it does not take in consideration the context path and we get a HTTP 404 page not found. Our context path we have set is /mirth. Full error is below.

{noformat} Unable to retrieve payload from HTTP request. URI: https://localhost:443/webstart/extensions/scriptfilestep.jnlp java.lang.Exception: Unable to retrieve payload from HTTP request. URI: https://localhost:443/webstart/extensions/scriptfilestep.jnlp at com.mirth.connect.client.launcher.f.a(SourceFile:782) at com.mirth.connect.client.launcher.f.a(SourceFile:662) at com.mirth.connect.client.launcher.f.a(SourceFile:307) at com.mirth.connect.client.launcher.MirthClientLauncher.run(SourceFile:1122) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.Exception: HTTP request returned invalid response. HTTP status: HTTP/1.1 404 Not Found, URI: https://localhost:443/webstart/extensions/scriptfilestep.jnlp at com.mirth.connect.client.launcher.f.a(SourceFile:771) ... 4 more {noformat}

Imported Comment. Original Details: Author: dre4967 Created: 2019-01-31T09:14:58.000-0800