Loading Profile...
Proxy problem with Scaffolded pages
After having added scaffolding code to a page it shows fine, but when trying to re-edit the page I'm it appears to time out before giving a HTTP Error 502: Proxy error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /iwiki/pages/ scaffold/editscaffold.action.
We're not sure yet if the problem are caused by the Proxy or by Scaffolding. Can you help?
We're not sure yet if the problem are caused by the Proxy or by Scaffolding. Can you help?
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
-
Inappropriate?Hi there,
I haven't seen this particular problem before, but I haven't tried using Scaffolding inside a proxied environment either. I'm not aware of anything special about the URL you list though.
I did notice that there seems to be an extra space "/pages/ scaffold", but this might just be a formatting issue in the report.
Are you getting any errors in the server's logfile? -
Inappropriate?Also, what version of Confluence and Scaffolding are you using?
-
Inappropriate?We're using Confluence 2.9.1 and Scaffolding 3.1.2, and yes that extra space was just a formatting glitch, it is not in the actual error message.
We're looking into errors in the server logs, but so far have found none that seem related. -
Inappropriate?Ok, it sounds like it could be the proxy server. The best way to test would be to try accessing the site on the server itself, via 'localhost' and seeing if you still get the error message. If not, there is probably a problem between you and the server.
-
Inappropriate?We found the error after checking the logs. It was caused by Scaffolding retrieving the entire 60.000 user LDAP database whenever it needed to look up users, even if limited to a single group or even a single person. This lookup naturally takes so long that both the proxy and afterwards the webserver times out. Regular scaffolds work as expected as long as they do not include any direct user-lookups.
The same problem also exists with the Reporting plugin, meaning that all the user-capabilities of both plugins are broken for us. Very annoying.
I found comments on another forum about the same issue, and there it was explained that it is caused by the LDAP-implementation of the Confluence lookup API, so there was nothing to do about it on your end. However that makes me wonder why working with LDAP-userstores works perfectly for Confluence functionality. Please look into this! -
Inappropriate?Well, there is probably some improvement that can be made to Scaffolding also. It is probably worth creating a bug report and we can investigate if there is anything that can be done at that end.
However, some versions of Confluence do not have good caching configured for LDAP. Check the following links and see if they help your situation:
LDAP Performance Tweaks
Poor Performance due to LDAP Cache with Incorrect Key
Performance Tuning
EMPLOYEE
