I believe your https is not configured properly. The dispatcher log will tell you the issue with request if you see the request coming to dispatcher with Https. Can you enable the dispatcher log with log level as trace or debug to get the logs for the request. This will help in tracing back what is ...

You can access the variable set in aem sightly as explained on https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-declare-a-variable-in-sightly/m-p/256691 but not sure if it will works in your case like sharing it among different repositories

Can you check the dispatcher log for such request. It will clearly mention which header field you need to update with. Do you have Akamai as well on your instance? If yes try updating it. Normally Akamai has default request header size as 32kb but Apache has 8 kb. can you check if your tenant specif...

For above use case to work you need to access the complete path of the component authored. So in your case it may be something similar to localhost:4502/content/my-site/my-page/jcr:content/componebt-location-on-page.print.html. but if you want the selector to work at  localhost:4502/content/my-site/...

I have work on the project that was implemented in the way @aanchal-sikka shared. Basically on aem component html page you put the dialog values on data- attributes and from the react js you can read the data-attributes and then render it via react dom. I do see one challenge in this approach of loa...

What outputs are you expecting. See below documentation for number formatting in aem using sightly. https://github.com/adobe/htl-spec/blob/master/SPECIFICATION.md#1223-numbers

In other components html you can use pageproperties.fieldName to get the value authored on page. Something similar to ${pageProperties.jcr:title}

You can’t directly pass a value from one component to another unless otherwise you are storing the value on page properties instead of components or uses cookie or local storage (not recommended)

Via package manager. You can place those images in your code base and deploy it on aem via package manager or maven build.

For local setup you need to run local universal editor as well. Details are on https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/local-dev