Closed GoogleCodeExporter closed 8 years ago
It seems like your server does not like the REST kind of URL formatting, for
example "/backend/r.php/session/info"
The point here is that PHP should execute "backend/r.php" and process query
with path "/session/info". Your server seems to complain that resource
"/backend/r.php/session/info" does not exist, and it certainly does not.
I can't remember there being another case where this does not work, so I don't
know what to do about it. Most likely it is configuration issue, but cannot
tell what to change.
Another possibility would be to change the URL syntax to something like
"/backend/r.php?p=/session/info", but this is not as clean as I'd like (would
have to be configuration option to choose this is have to) and would require
changes in both sides, client and server so that URLs are generated and parsed
accordingly.
Original comment by samuli.j...@gmail.com
on 11 Nov 2014 at 9:25
Same issue here. I get a "Failed to initialize Mollify". I also get the popup
"Request failed", but I don't get qany errors in Apache access log:
10.20.141.79 - - [30/Dec/2014:12:10:54 +0100] "GET /mollify/backend/install/
HTTP/1.1" 200 58
10.20.141.79 - - [30/Dec/2014:12:10:55 +0100] "GET /favicon.ico HTTP/1.1" 404
11408
10.20.141.79 - - [30/Dec/2014:12:10:55 +0100] "GET /favicon.ico HTTP/1.1" 404
11408
10.20.141.79 - - [30/Dec/2014:12:11:01 +0100] "GET
/mollify/templates/dialogs.html?_=1419937886796 HTTP/1.1" 200 4372
10.20.141.79 - - [30/Dec/2014:12:11:01 +0100] "GET
/mollify/backend/r.php/session/info/ HTTP/1.1" 200 289
10.20.141.79 - - [30/Dec/2014:12:11:01 +0100] "GET
/mollify/js/lib/ZeroClipboard.swf?nocache=1419937886857 HTTP/1.1" 200 1965
I have a working 2.5.17 version but can't manage to get 2.5.18 or 2.5.19
version running properly.
Original comment by joaki...@gmail.com
on 30 Dec 2014 at 11:22
#2: Don't look at the Apache access logs, it simply lists requests made through
Apache, but this is not about Apache. Look at the PHP error log.
Original comment by samuli.j...@gmail.com
on 31 Dec 2014 at 10:19
The initial issue will not be handled, this is the only time I have heard this,
and it sounds like server configuration issue. Second comment is too vague to
handle, if there is more info it should be opened as separate issue.
Original comment by samuli.j...@gmail.com
on 1 Jan 2015 at 6:54
Original issue reported on code.google.com by
ranganat...@intuitivcloud.com
on 5 Nov 2014 at 6:53