[
https://issues.apache.org/jira/browse/COUCHDB-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956895#comment-13956895
]
ASF GitHub Bot commented on COUCHDB-2206:
-----------------------------------------
Github user robertkowalski commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/202#discussion_r11175110
--- Diff: src/fauxton/tasks/couchserver.js ---
@@ -51,6 +51,7 @@ module.exports = function (grunt) {
filePath = path.join(app_dir, url.replace('/_utils/fauxton/',''));
} else if (!!url.match(/assets/)) {
// serve any javascript or css files from here assets dir
+ url = url.replace(/\?.*/, '');
--- End diff --
ZeroClipboard is adding a GET-parameter with the unix-timestamp when it is
requesting the `swf` to bust browser-caches. It requests something like this
`http://localhost:8080/plugins/zeroclipboard.swf?131231234`.
The node server is taking any url and is mapping it directly to a path on
the filesystem, but a file named `zeroclipboard.swf?131231234` does not exist,
the filename we have to search for on the disk is `zeroclipboard.swf` and
therefore the server returns a 404 error.
So if we are requesting files with a `GET`-Parameter we have to slice it
off, or implement another solution that reacts to the `GET`-Parameter - but
until now there is no use-case for reacting to `GET`-Parameters.
> Changes UI update
> -----------------
>
> Key: COUCHDB-2206
> URL: https://issues.apache.org/jira/browse/COUCHDB-2206
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Fauxton
> Reporter: Sue Lockwood
> Assignee: Robert Kowalski
> Attachments: Screen Shot 2014-03-22 at 9.46.15 AM.png, Screen Shot
> 2014-03-22 at 9.46.38 AM.png
>
>
> The changes UI needs some serious love.
> The new UI improvements are being broken down into parts so that we can get
> them into master easier. I have screenshots of just what the changes page UI
> should look like.
> I cropped out the sidebar and header for now, since those changes are being
> made in a different branch and are used all over the site. They should be in
> soon.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
