emely flexible.
I do not currently have my configuration page but would be happy to share
it if it clarifies things. I'm quite befuddled by the results myself.
Please let me know any further clarifications I can make.
Last thing to note: I tested this configuration with a second project that
h
e know if you'd like any
more details. I apologize for my vagueness and ambiguity so thank you for
sticking with me on it.
On Thu, Aug 27, 2015 at 12:12 AM, Kurtis Rader wrote:
> On Tue, Aug 25, 2015 at 10:25 PM, Steven Shi
> wrote:
>
>> The "app" consists of
ecause jetty typically would listen on port 80
> and is on a different server from the app but you have a need for app and
> jetty on the same server so the jetty needed an alternate port?
>
> Robert
>
>
>
> On Tue, 25 Aug 2015 13:52:07 -0400
>
> Steven Shi wrote:
>
jquery for requests.
The remote IP as shown from the developers console in Google chrome. I
looked at the failed GET request.
I know the problem is not caused by the SSL rewrite (tested by turning of
SSL module).
On Tue, Aug 25, 2015 at 1:28 AM, Kurtis Rader wrote:
> On Mon, Aug 24, 2015 at 9:52 P
aight to localhost:2000, the app works as intended and makes all
requests to localhost:2000/request while showing the remote IP to be
localhost:2000.
On Tuesday, August 25, 2015, Kurtis Rader wrote:
> On Mon, Aug 24, 2015 at 8:30 PM, Steven Shi > wrote:
>
>> I'm trying to pro
I'm trying to proxy /app to localhost:2000 (where the app is hosted).
Unfortunately, whenever the app makes a GET/POST request, the port 2000 is
lost and the request is made to localhost:80 rather than localhost:2000.
I feel as if the solution is something simple but I haven't been able to
discove
