Changing img src relative links to absolute | Community
Skip to main content
benn28474296
Level 2
Jan 24, 2019 6:35 PM UTC
Solved

Changing img src relative links to absolute

We're using experience fragments to produce HTML fragments that are consumed and displayed by an external application.  Since the html in that case is no longer being served by the AEM instance we need any assets to be referenced by an absolute path rather then a relative one.  I've seen some older blog posts that mention modifying the externalizer but I was wondering if that's still the only option and if so if there's better documentation available.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Gaurav-Behl
Gaurav-BehlAccepted solution
Level 10
Jan 25, 2019 4:34 PM UTC

OOB features like Externalizer, Transformers, Sling Rewriters etc. would require custom coding & configuration.

If you don't want to create any custom components in AEM then you may achieve this use case in apache/dispatcher; write a cron to parse cached fragments and replace urls or use mod_proxy, mod_substitute etc. to modify response. It depends on the current setup and feasibility based on your use case.

View reply

7 replies

Gaurav-Behl
Gaurav-Behl
Level 10
Jan 29, 2019 1:12 AM UTC

I found another interesting solution (configuration based) for this use case, may be for future use cases...

Static Reference Rewriter

Translate
benn28474296Author
Level 2
Jan 26, 2019 4:25 AM UTC

OK, I just ended up making a custom Transformer since I was only really worried about img tags for this use case.

Translate
Gaurav-Behl
Gaurav-BehlAccepted solution
Level 10
Jan 25, 2019 4:34 PM UTC

OOB features like Externalizer, Transformers, Sling Rewriters etc. would require custom coding & configuration.

If you don't want to create any custom components in AEM then you may achieve this use case in apache/dispatcher; write a cron to parse cached fragments and replace urls or use mod_proxy, mod_substitute etc. to modify response. It depends on the current setup and feasibility based on your use case.

Translate
benn28474296Author
Level 2
Jan 25, 2019 8:38 AM UTC

No, we're just publishing experience fragments in a very stripped down template to produce an html fragment.  The number/types of component's being used might change from page to page and we don't want the downstream application to need to process any json at all.  We just want each to produce a single fragment of simple html that can be included.  It's working great so far, except for the relative links.

Translate
smacdonald2008
smacdonald2008
Level 10
Jan 25, 2019 6:05 AM UTC

Are you using Content Services?

Translate
benn28474296Author
Level 2
Jan 24, 2019 11:32 PM UTC

No, the html fragments are being consumed by an angular app and injected into it so there's no iframe.  The needs for the content are fairly simple so we are hoping to just work with the out of the box components.  I'd rather not create custom components if I can avoid it

Translate
Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
Jan 24, 2019 8:51 PM UTC

If you are including the HTML fragments in an iframe within an external application, then that page will be served from AEM in which case the externalizer helps.

if not another way I can think of is to handle that within your component renderer (HTML). When you read the image link and add that value in your html, make it as an absolute path (if you want to hardcode the domain or read it from the browser)

Translate
Terms & ConditionsAccessibility statement

Loading footer...