Opened 10 years ago

Last modified 10 years ago

#1848 new defect

Possible intermittent bug in "test with file" interface (Firefox with "buffer app" add-on!)

Reported by: base Owned by: everyone
Priority: minor Milestone:
Component: web Version: 3.3
Keywords: Cc:


Hi guys,

I'm not 100% sure this is reproducible....

I normally use Firefox, but twice now I've seen nothing happen after configuring a plugin with "test with file" ... (choose the file) ... "parse the file".

The first time I thought it was due to a recent raw-data-types upgrade on the server - so I restarted it and it seemed to be fixed.

Now I'm getting it again, and without restarting the server I see it works fine in Chrome.

Previously I had looked in the tomcat logs and ignored entries like this:

13:41:19,616  WARN ContentSecurityPolicyReportServlet:64 - {"csp-report":{"document-uri":"","referrer":"","blocked-uri":"","violated-directive":"default-src"}}

But now I see that these log entries don't appear when using Chrome and could be relevant. There are no stack traces or anything more useful, sorry!

Googling I see that this could be a clash with the "buffer app" firefox addon. I'll need to do some tests restarting my browser so, I'll save this ticket and comment on it further as required....

Change History (4)

comment:1 by base, 10 years ago

By the way, this is Bob MacCallum here...

I've disabled some of Buffer App's features (all except Twitter integration) and restarted firefox and now the test with file interface works (but that could have simply been the restart!)

If this happens again I'll disable the add-on altogether and continue testing.

comment:2 by Nicklas Nordborg, 10 years ago

The entry in the log file you is a report that something is trying to download a document from which is blocked by the "Content security policy".

The is a javascript and I would suspect that it is related to the Buffer app based on the fact that the script is calling a method called bufferpm().

So, basically, I think that the addon is inserting code into the BASE web client and trying to do stuff but this is blocked by BASE. I don't know why this should cause BASE to stop working...

If this app is important to you there is always the possibility to modify the Content Security Policy so that it doesn't block Most of what you need to do this can be found in the web.xml file.

comment:3 by Nicklas Nordborg, 10 years ago

I found this discussion about a similar issue with Chrome:

Seems like it was a bug in Chrome when an extension tries to insert an <iframe> into the document. I am not sure if it is completely fixed in Chrome or not, but if the Buffer extension is not working it is probably due to a bug in the browser.

On the other hand, this should not stop BASE from working. If you see this issue again, can you check if there is anything in the debug console in Firefox (open it by pressing CTRL+SHIFT+K)?

comment:4 by base, 10 years ago

Thanks Nicklas. We will keep you posted with any further diagnosis or developments.

Note: See TracTickets for help on using tickets.