# Builder Editor - Iframe view blocked by Cloudfront due to invalid character in query Parameter

**URL:** <https://forum.builder.io/t/builder-editor-iframe-view-blocked-by-cloudfront-due-to-invalid-character-in-query-parameter/4223>\
**Category:** Bugs\
**Created:** [September 21, 2023, 11:18am UTC](https://forum.builder.io/t/builder-editor-iframe-view-blocked-by-cloudfront-due-to-invalid-character-in-query-parameter/4223 "2023-09-21T11:18:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![samcoleman](https://avatars.discourse-cdn.com/v4/letter/s/d6d6ee/32.png) [@samcoleman](https://forum.builder.io/u/samcoleman)\
**Post date:** [September 21, 2023, 11:18am UTC](https://forum.builder.io/t/builder-editor-iframe-view-blocked-by-cloudfront-due-to-invalid-character-in-query-parameter/4223/1 "2023-09-21T11:18:32Z")

</div>

I have already mentioned this on a Bug posted on May 4th but I have had no response to it so I am posting on a fresh feed.

**Builder content link**

N/A - Applies to any Builder Editor View

**Builder public api key**  
1926e37b53694b938d73f2c1b9f36bfd

**Detailed steps to reproduce the bug**

1. Create a Next.js application for Builder
2. Deploy it with SST (which deploys it to AWS)
3. Try to create a page and preview it via Builder

Notice that on step 3, you’ll get the following error:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/builder/original/2X/5/5794c4a9e3afb4adfadc6c69a570886e3b654740.png)

This is the query that CloudFront is blocking, “:” characters are not allowed in query parameters.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/builder/original/2X/7/70bf57ae5ff15c22cbf2f29f72723f68115e3d40.png)  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/builder/original/2X/c/c6c3612827761f17df8116d506df53bb44a32c85.png)

I have been unable to find a way to configure AWS to ignore this problem. The only workaround I have found is to edit the query in the iframe of the visual builder, allowing me to live edit and publish changes. However, this is not optimal as I have to do this every time I load the page.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/builder/original/2X/c/c40b9a70433837906bb1eeb35fe1a3cfa3693fe9.png)

**Code stack you are integrating Builder with**  
Next.js, SST, & AWS.

---

<div class="post-metadata">

**Author:** ![OmPrakash](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.builder.io/omprakash/32/2751_2.png) [@OmPrakash](https://forum.builder.io/u/OmPrakash)\
**Post date:** [October 20, 2023, 9:43am UTC](https://forum.builder.io/t/builder-editor-iframe-view-blocked-by-cloudfront-due-to-invalid-character-in-query-parameter/4223/2 "2023-10-20T09:43:51Z")

</div>

Hi @samcoleman,  
Sorry about the delay, wanted to check issue still persists for you?

---

<div class="post-metadata">

**Author:** ![samcoleman](https://avatars.discourse-cdn.com/v4/letter/s/d6d6ee/32.png) [@samcoleman](https://forum.builder.io/u/samcoleman)\
**Post date:** [October 20, 2023, 10:42am UTC](https://forum.builder.io/t/builder-editor-iframe-view-blocked-by-cloudfront-due-to-invalid-character-in-query-parameter/4223/3 "2023-10-20T10:42:21Z")

</div>

Hi @OmPrakash, I have just checked and yes this problem still persists.

I can still workaround the issue for now by changing the Iframe src as before

---

<div class="post-metadata">

**Author:** ![OmPrakash](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.builder.io/omprakash/32/2751_2.png) [@OmPrakash](https://forum.builder.io/u/OmPrakash)\
**Post date:** [October 20, 2023, 11:11am UTC](https://forum.builder.io/t/builder-editor-iframe-view-blocked-by-cloudfront-due-to-invalid-character-in-query-parameter/4223/4 "2023-10-20T11:11:47Z")

</div>

Thank you for your response, @samcoleman . We are investigating the matter and will reach out if we require additional information or have updates to share.

---

<div class="post-metadata">

**Author:** ![sheema](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@sheema](https://forum.builder.io/u/sheema)\
**Post date:** [November 20, 2023, 9:47am UTC](https://forum.builder.io/t/builder-editor-iframe-view-blocked-by-cloudfront-due-to-invalid-character-in-query-parameter/4223/5 "2023-11-20T09:47:25Z")

</div>

@samcoleman can you please include a content URL or the URL that is getting blocked?

Could you please compare the URL that is getting blocked to a working URL for a different page to see if both of them have the encoded “:” in the URL. If the working URL has the “:” encoded, then it’s a problem with the integration.

---

<div class="post-metadata">

**Author:** ![sheema](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@sheema](https://forum.builder.io/u/sheema)\
**Post date:** [November 23, 2023, 9:15am UTC](https://forum.builder.io/t/builder-editor-iframe-view-blocked-by-cloudfront-due-to-invalid-character-in-query-parameter/4223/6 "2023-11-23T09:15:24Z")

</div>

@samcoleman We were able to track it down. SST adds a cloudfront function which seems to be doing the blocking.

You can change the SST code to change these query strings to be able to proceed.

For example, in the cloudfront function SST generated, change

```auto
function handler(event) {
  var request = event.request;
  request.headers["x-forwarded-host"] = request.headers.host;
  return request;
}

```

to

```auto
function handler(event) {
  var request = event.request;
  console.log('REQUEST----', event.request.querystring);
  if (event.request.querystring['builder.overrides.page:/']) {
      event.request.querystring['builder.overrides.page'] = event.request.querystring['builder.overrides.page:/'];
      delete event.request.querystring['builder.overrides.page:/'];
  }
  request.headers["x-forwarded-host"] = request.headers.host;
  return request;
}

```

The above is just a hack, but it gets the request serving again