What entry do you see in dispatcher log? Can you start the dispatcher in debug mode to check what happening for this request ?

Please take a look at below documentation  https://blog.3sharecorp.com/shortening-urls-in-aemhttps://helpx.adobe.com/ca/experience-manager/kb/multi-domain-management-aem-mappings-for-url-shortening---aem-6-.html and follow the process that best suits your requirements 

My recommendation would be to create a sling job and execute the workflow from there to do following things. check out the assets(similar to locking pages) so that no one can do any edit or publish the assetUnpublishUnpublish in Dynamic Media.Unpublish from Brand.Check in again might not required if...

https://adobe-consulting-services.github.io/acs-aem-commons/features/environment-indicator/index.html

Not necessarily, you can read dialog properties on their respective html by using {properties.fieldName} in case you are not having any back end logic for the dialog and if you need some logic or manipulation on the data you can surely write your componentModel.java and it’s test class 

You can use something like this  <div id="${models.id}" class="cmp-container" style="max-height: ${properties.maxHeight @ context="styleString"}px">  <!-- Your content here --></div>  so in your case it going to be <pre style="height:${properties.maxHeight @ context="styleString"}px"> </pre> to lea...

ValidationViolation: "jackrabbit-nodetypes: This error message suggest that it’s failing to validate the node type of the node. If you don’t define the node type it will consider as folder, default behaviour. If you check the log in details it’s complaining that you are trying to set the node proper...

In AMS author and publisher are both behind the dispatcher. Please check the filter rules in dispatcher configs for author, if you are allowing the servlet path in allow rule. Should have similar dispatcher configuration on author for this servlet like dispatcher for publisher.  

If you setup your aem publisher correctly with publish run mode it’s available by default. No customization needed to access /content and /etc.clientlibs. You can check the run mode on aem publish instance to make sure that it’s run mode is setup as publish. Secondly, you can also check the access l...

It seems a wiered requirement that you need a login on aem publisher for serving the content. normally Aem publisher has anonymous user that has permission for /content and /etc.clientlibs to serve the pages, assets and clientlibs anonymously without requiring you to login and dispatcher will severs...