Closed CTRL-V of images results in error

[Mike Fara]

Affected version

XenForo 2.0

Environment is Windows 10 under the latest Chrome.






Lets try this on XenForo.com:



No issue. I was asked to post this here as a bug, but it appears to be something on my forum.

 

[Kier]

On your own forum, can you attach images and insert them into messages using the 'Attach files' button, rather than a ctrl+v?

 

[Mike Fara]

On your own forum, can you attach images and insert them into messages using the 'Attach files' button, rather than a ctrl+v?

Yes. That actually works fine.

 

[Mike Fara]

Is there any resolution for this issue?

 

[Mike]

Can you open the Chrome developer tools and go to the network tab when you try to paste an image in? Do you see anything red there off hand? Would it be possible to screenshot the contents of that tab?

 

[Mike Fara]

 

[Mike Fara]

• Queueing. The browser queues requests when:
  • There are higher priority requests.
  • There are already six TCP connections open for this origin, which is the limit. Applies to HTTP/1.0 and HTTP/1.1 only.
  • The browser is briefly allocating space in the disk cache
• Stalled. The request could be stalled for any of the reasons described in Queueing.

 

[Chris D]

There doesn't appear to be an explicit error there, but it may be worth looking under the Console tab which does look as though it could have an error message.

 

[Mike Fara]

post-thread:1 Refused to load the image 'blob:https://windowsforum.com/a63cb1b2-039a-42fb-bd7d-19a4c4ce4c68' because it violates the following Content Security Policy directive: "img-src * data:".

Looks like its the content security policy in .htaccess. There could be some improper formatting there so I am looking at that now.

 

[Mike Fara]

I believe it to be a potential error in our content-security-policy string in .htaccess and NOT a XenForo bug. Therefore this bug is most likely not a bug - but a configuration error. The string we use is very long and complex, and probably not for a very good reason. All is well and thanks for your suggestions. Basic debugging would have resolved the problem - time constraints prevented this. Thank you.