-
Notifications
You must be signed in to change notification settings - Fork 58
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
Unable to run setup on HTTPS + proxy'd sub-path #1652
Comments
The config below works for me, as long as I complete the setup on http://example.com:8080. You may need to change
|
Thanks, so Proxy'd My browser is Firefox (latest version no plugins/blocking) I'm using the WAR with tomcat 7.x whenever I submit setup2.do it returns to the same page and claims that nothing has been submitted. I checked and confirmed post data is being sent from firefox. So this has got to be an app problem. When's the last time you setup IPT from scratch, and are you using the WAR? |
@vollmerk I tried with the latest version (2.5.1) using Docker, as well as in a Tomcat subfolder like you did. For the latter case I had to change my config to This is what the POST request looks like, so the |
What version of tomcat are you using? Yeah I never get the redirect to setup3, just a kick back to setup2 claiming I submitted none of the values. |
Is what I'm running. |
I tested with Tomcat 8.5 on Java 8 before, but I did a quick check with a (Dockerized) Tomcat 7.0.76 on OpenJDK 8 and that worked fine as well. If you do not need your Tomcat for other purposes you may want to look into the IPT Docker image, it works like a charm. |
So I managed to get this going using the docker container, but I noticed some additional things
So there's definitely some overly aggressive error checking, and non-proxy/path friendly code during the setup |
Might the change suggested here help: #1470 (comment) |
@MattBlissett - That's the opposite problem I have it running on / and proxy'd from /ipt. Either way I forced the cookie path and the problems persist. It's down to I can get it to run, when /ipt/login.do is run it accepts the authentication, sets the cookie properly but then re-directs to / instead of /ipt. / is a different application :D I haven't looked at the code yet, but I'm guessing that the login processing doesn't account for the defined path and just redirects to / on success. |
Pieter's Nginx + Docker configuration works for me with the current snapshot, including with Docker exposing port 8082. Using I've added the Nginx configuration to the documentation. I think it helps to have the IPT's internal path (e.g. |
I think this is improved for 2.5.2. (The missing Bootstrap file is for Javascript debugging, it's not included so the error is expected.) |
We run IPT behind an NGINX proxy over SSL in a sub-path and when submitting the setup form, the HTTP POST is sent with the correct data, but the application does not think it received anything
https://example.com/ipt (NGINX entry point)
Proxy to
http://127.0.0.1:8080 (IPT Tomcat instance)
baseURL is set correctly, as all of the image urls are generated correctly
I did note that the <form action="setup2.do" does not include ${baseURL}, adding that manually doesn't make any difference.
...
I also note that there appears to be a missing referenced bootstrap file
The text was updated successfully, but these errors were encountered: