Subassets won't publish and are giving 404's in publish instance

[laniweisbart]

We have created a feature that needs access to each asset's subassets.  But our subassets are not showing up in publish.  We do not have a publish option on the subassets folder.  Treeactivation does not seem to be working either.  And when we ran the subassets through the ActivationModel workflow, they each have an indicator that makes it appear as if they are published, yet they still do not show up in Publish - they all throw 404's.  

Is this a bug or is there a way to make subassets available on Publish?

[Saravanan_Dharmaraj]

@laniweisbart Have you seen the log in replication queue and do you see error in the log when you did Tree activation?  

[laniweisbart]

I was able to get some subassets to publish via tree activation but we are still getting 404's on publish.  Are there certain permissions needed to make subassets available on publish?

[Tethich]

Do you have a way to visually access the publish instance data ? I believe in AEMaaCS you can have the Repository Browser. And sometimes in on-prem publish it can also be available if you can like open with /login path. My aim is to actually confirm the assets are not there.

[laniweisbart]

Yes I am able to see the subassets via crxde on both Author and Publish.  So the subassets are there in Publish but still throwing 404s when we present them to the page.  In Author we do not receive 404s.

[Tethich]

Do you access directly yhe publish domain or via Dispatcher ? I am inclined to think you might have a blocking rule in Dispatcher.

[Tethich]

Do you have AEMaaCS or on-prem ? Does the issue happen in local as well ?

[laniweisbart]

We are on-prem.  We are currently on Service pack 21 and also using Asset Share 3.8.4.

[laniweisbart]

Also confirmed the issue does not happen in local - the subassets are working showing up in both Author and Publish.

[Tethich · Accepted solution]

Are you using Dispatcher in local ? Cause it might be some rule there that forbids on remote env access to some path from assets or somethig. Can you check your .any files ?

[laniweisbart]

Thank you for your help.  The issue was in fact related to the dispatcher config.  The solution was not intuitive at all but the correct configuration ended up looking like this:

/0404 { /type "allow" /method "GET" /path "/content/dam/[customfolder]/*" /suffix '^/subassets/.*' /extension '(mov|mp4|mp5)' }  

We had to turn on trace logging to see how the dispatcher was decomposing the url's for the subassets in order to arrive at this solution.