By the way, is this documented anywhere?

From: William Crowell <wcrow...@perforce.com.INVALID>
Date: Wednesday, July 2, 2025 at 2:12 PM
To: users@activemq.apache.org <users@activemq.apache.org>
Subject: Re: What changed between ActiveMQ Classic 6.1.6 and 6.1.7 where the 
images do not show up on the web user interface?

Disregard.  I guess you have to comment out lines 84-88 of jetty.xml:

...
<!--
                <bean id="header" 
class="org.eclipse.jetty.rewrite.handler.HeaderPatternRule">
                    <property name="pattern" value="*"/>
                    <property name="name" value="Content-Security-Policy"/>
                    <property name="value" value="upgrade-insecure-requests; 
style-src-elem 'self'; style-src 'self'; img-src 'self'; script-src-elem 
'self'; default-src 'none'; object-src 'none'; frame-ancestors 'none'; base-uri 
'none';" />
                </bean>
-->
...

Regards,

William Crowell


From: William Crowell <wcrow...@perforce.com.INVALID>
Date: Wednesday, July 2, 2025 at 12:37 PM
To: 'users@activemq.apache.org' <users@activemq.apache.org>
Subject: What changed between ActiveMQ Classic 6.1.6 and 6.1.7 where the images 
do not show up on the web user interface?

Good afternoon,

What changed between ActiveMQ Classic 6.1.6 and 6.1.7 where the images do not 
show up on the web user interface?

6.1.7 release notes:
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FReleaseNote.jspa%3FprojectId%3D12311210%26version%3D12355749&data=05%7C02%7CWCrowell%40perforce.com%7C960e4bf2f7b54f96d4c608ddb993f334%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638870767282544742%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=SsWzRJTQNxhSLutBcxCKRIy94xqxSFYR5%2BY5siKyraY%3D&reserved=0<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FReleaseNote.jspa%3FprojectId%3D12311210%26version%3D12355749&data=05%7C02%7CWCrowell%40perforce.com%7C960e4bf2f7b54f96d4c608ddb993f334%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638870767282620905%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=930Skehy%2BXCVZkYUwowvLnqwJpv56nuqKskfvtRAK3I%3D&reserved=0><https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12355749>

I have changed jetty.xml (which is the only thing I have changed since 
untarring apache-activemq-6.1.7-bin.tar.gz), so that the broker listens on all 
IP addresses.  It appears that the images and .css are not rendering correctly 
on the 8161 port management console, and everything seems to want to use https.

Was it this change?  
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FAMQ-9697&data=05%7C02%7CWCrowell%40perforce.com%7C960e4bf2f7b54f96d4c608ddb993f334%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638870767282679209%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=KZcPQ3QJ%2Bcfc00UvPUx3iM6CmkrXxDnhqJQMNfl2Frg%3D&reserved=0<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FAMQ-9697&data=05%7C02%7CWCrowell%40perforce.com%7C960e4bf2f7b54f96d4c608ddb993f334%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638870767282738171%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=uKyrWuFq9rgTkfn91bFuyGPJNKS%2F7sOPHowPTEL%2BZSU%3D&reserved=0><https://issues.apache.org/jira/browse/AMQ-9697>

How do you fix this?

Regards,

William Crowell


This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

Reply via email to