Hi all,
i start httpgate with:
$ bin/httpGate 3000 8080 8081 8082
then run the sample app.
it shows me the login screen and then the location in the browser points at:
http://192.168.1.253:3000/45313/713963214703762...@start?*menu=+3*Tab=+1*ID=
which shows a blank page. console shows:
Hi Edwin,
$ bin/httpGate 3000 8080 8081 8082
...
http://192.168.1.253:3000/45313/713963214703762...@start?*menu=+3*Tab=+1*ID=
Oops, you found a bug! At least (and to my own surprise), it doesn't
work that way. I must confess I never tested with ports different from
the protocol-specific
On Tue, Aug 24, 2010 at 12:38:28PM +0200, Alexander Burger wrote:
If such a setup were indeed necessary (e.g. because you have no
permission to start 'httpGate' at port 443, but you need it for HTTPS),
then the protocol between 'httpGate' and the application server would
need to be extended a
Hi Alex,
Do you need this kind of setup for some special reason? After all, the
not really. i was just using it for tests. i didn't even give port 80
a shot yet. :).
main purpose of 'httpGate' is to proxy all requests to the default port
to app-specific ports like 8080. If you pass :3000 to
Hi Alex,
will try the usual port and if i don't succeed, then it will be a concern.
it is a concern.
$ ./bin/httpGate 80 8080
gives the same result.
cheers,
/e
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
Hi Edwin,
On Tue, Aug 24, 2010 at 12:54:53PM +0200, Alexander Burger wrote:
On Tue, Aug 24, 2010 at 12:38:28PM +0200, Alexander Burger wrote:
If such a setup were indeed necessary (e.g. because you have no
...
Forget that. It is in fact a new bug!
It used to work in the past. Let me
