How can I change status code in viewer-response Cloudfront event?











up vote
1
down vote

favorite












I want to secure Cloudfront response using S3 object metadata and some role data in DB (or some remote service), specif for current user. I think I should use viewer-response event here, to have access to S3 data and user data together. I try to set status and statusDescription in response object, but it does not work for viewer-response event, works for all other events. Setting headers still works.



exports.handler = async (event) => {

const response = event.Records[0].cf.response;
const request = event.Records[0].cf.request;
const isUserAllowed = await allowedByTokenAndDb(request);
const isS3ObjectAllowed = response.headers['x-amz-meta-isSecure'][0].value === 'true';

if (!isUserAllowed || !isS3ObjectAllowed) {
response.status = '403'; // does not work
response.statusDescription = 'Nothing';
}

response.headers['X-Powered-By'] = [{ // works, header will be added
key: 'X-Powered-By',
value: 'lol',
}]

return response;
}


Is there any way to make viewer-response return another status? AWS documentation does not tell that it is possible or not. Maybe there is another solution?










share|improve this question


























    up vote
    1
    down vote

    favorite












    I want to secure Cloudfront response using S3 object metadata and some role data in DB (or some remote service), specif for current user. I think I should use viewer-response event here, to have access to S3 data and user data together. I try to set status and statusDescription in response object, but it does not work for viewer-response event, works for all other events. Setting headers still works.



    exports.handler = async (event) => {

    const response = event.Records[0].cf.response;
    const request = event.Records[0].cf.request;
    const isUserAllowed = await allowedByTokenAndDb(request);
    const isS3ObjectAllowed = response.headers['x-amz-meta-isSecure'][0].value === 'true';

    if (!isUserAllowed || !isS3ObjectAllowed) {
    response.status = '403'; // does not work
    response.statusDescription = 'Nothing';
    }

    response.headers['X-Powered-By'] = [{ // works, header will be added
    key: 'X-Powered-By',
    value: 'lol',
    }]

    return response;
    }


    Is there any way to make viewer-response return another status? AWS documentation does not tell that it is possible or not. Maybe there is another solution?










    share|improve this question
























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I want to secure Cloudfront response using S3 object metadata and some role data in DB (or some remote service), specif for current user. I think I should use viewer-response event here, to have access to S3 data and user data together. I try to set status and statusDescription in response object, but it does not work for viewer-response event, works for all other events. Setting headers still works.



      exports.handler = async (event) => {

      const response = event.Records[0].cf.response;
      const request = event.Records[0].cf.request;
      const isUserAllowed = await allowedByTokenAndDb(request);
      const isS3ObjectAllowed = response.headers['x-amz-meta-isSecure'][0].value === 'true';

      if (!isUserAllowed || !isS3ObjectAllowed) {
      response.status = '403'; // does not work
      response.statusDescription = 'Nothing';
      }

      response.headers['X-Powered-By'] = [{ // works, header will be added
      key: 'X-Powered-By',
      value: 'lol',
      }]

      return response;
      }


      Is there any way to make viewer-response return another status? AWS documentation does not tell that it is possible or not. Maybe there is another solution?










      share|improve this question













      I want to secure Cloudfront response using S3 object metadata and some role data in DB (or some remote service), specif for current user. I think I should use viewer-response event here, to have access to S3 data and user data together. I try to set status and statusDescription in response object, but it does not work for viewer-response event, works for all other events. Setting headers still works.



      exports.handler = async (event) => {

      const response = event.Records[0].cf.response;
      const request = event.Records[0].cf.request;
      const isUserAllowed = await allowedByTokenAndDb(request);
      const isS3ObjectAllowed = response.headers['x-amz-meta-isSecure'][0].value === 'true';

      if (!isUserAllowed || !isS3ObjectAllowed) {
      response.status = '403'; // does not work
      response.statusDescription = 'Nothing';
      }

      response.headers['X-Powered-By'] = [{ // works, header will be added
      key: 'X-Powered-By',
      value: 'lol',
      }]

      return response;
      }


      Is there any way to make viewer-response return another status? AWS documentation does not tell that it is possible or not. Maybe there is another solution?







      amazon-cloudfront aws-lambda-edge






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 9 at 15:42









      Aliaksei Shytkin

      26226




      26226
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          This function demonstrates how you can update the response status to 200 and generate static body content to return to the viewer in the following scenario:


          The function is triggered in an origin response



          The response status from the origin server is an error status code (4xx or 5xx)





           'use strict';

          exports.handler = (event, context, callback) => {
          const response = event.Records[0].cf.response;

          /**
          * This function updates the response status to 200 and generates static
          * body content to return to the viewer in the following scenario:
          * 1. The function is triggered in an origin response
          * 2. The response status from the origin server is an error status code (4xx or 5xx)
          */

          if (response.status >= 400 && response.status <= 599) {
          response.status = 200;
          response.statusDescription = 'OK';
          response.body = 'Body generation example';
          }

          callback(null, response);
          };





          share|improve this answer





















          • It works for origin-response trigger, but it does not work for viewer-response, as I mentioned. I want to run my code on each request, use Cloudfront cache and have access to cached object. Now the closest thing I can have is to set cache timeout to 0 and use origin-response trigger.
            – Aliaksei Shytkin
            Nov 20 at 9:26











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228881%2fhow-can-i-change-status-code-in-viewer-response-cloudfront-event%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote













          This function demonstrates how you can update the response status to 200 and generate static body content to return to the viewer in the following scenario:


          The function is triggered in an origin response



          The response status from the origin server is an error status code (4xx or 5xx)





           'use strict';

          exports.handler = (event, context, callback) => {
          const response = event.Records[0].cf.response;

          /**
          * This function updates the response status to 200 and generates static
          * body content to return to the viewer in the following scenario:
          * 1. The function is triggered in an origin response
          * 2. The response status from the origin server is an error status code (4xx or 5xx)
          */

          if (response.status >= 400 && response.status <= 599) {
          response.status = 200;
          response.statusDescription = 'OK';
          response.body = 'Body generation example';
          }

          callback(null, response);
          };





          share|improve this answer





















          • It works for origin-response trigger, but it does not work for viewer-response, as I mentioned. I want to run my code on each request, use Cloudfront cache and have access to cached object. Now the closest thing I can have is to set cache timeout to 0 and use origin-response trigger.
            – Aliaksei Shytkin
            Nov 20 at 9:26















          up vote
          1
          down vote













          This function demonstrates how you can update the response status to 200 and generate static body content to return to the viewer in the following scenario:


          The function is triggered in an origin response



          The response status from the origin server is an error status code (4xx or 5xx)





           'use strict';

          exports.handler = (event, context, callback) => {
          const response = event.Records[0].cf.response;

          /**
          * This function updates the response status to 200 and generates static
          * body content to return to the viewer in the following scenario:
          * 1. The function is triggered in an origin response
          * 2. The response status from the origin server is an error status code (4xx or 5xx)
          */

          if (response.status >= 400 && response.status <= 599) {
          response.status = 200;
          response.statusDescription = 'OK';
          response.body = 'Body generation example';
          }

          callback(null, response);
          };





          share|improve this answer





















          • It works for origin-response trigger, but it does not work for viewer-response, as I mentioned. I want to run my code on each request, use Cloudfront cache and have access to cached object. Now the closest thing I can have is to set cache timeout to 0 and use origin-response trigger.
            – Aliaksei Shytkin
            Nov 20 at 9:26













          up vote
          1
          down vote










          up vote
          1
          down vote









          This function demonstrates how you can update the response status to 200 and generate static body content to return to the viewer in the following scenario:


          The function is triggered in an origin response



          The response status from the origin server is an error status code (4xx or 5xx)





           'use strict';

          exports.handler = (event, context, callback) => {
          const response = event.Records[0].cf.response;

          /**
          * This function updates the response status to 200 and generates static
          * body content to return to the viewer in the following scenario:
          * 1. The function is triggered in an origin response
          * 2. The response status from the origin server is an error status code (4xx or 5xx)
          */

          if (response.status >= 400 && response.status <= 599) {
          response.status = 200;
          response.statusDescription = 'OK';
          response.body = 'Body generation example';
          }

          callback(null, response);
          };





          share|improve this answer












          This function demonstrates how you can update the response status to 200 and generate static body content to return to the viewer in the following scenario:


          The function is triggered in an origin response



          The response status from the origin server is an error status code (4xx or 5xx)





           'use strict';

          exports.handler = (event, context, callback) => {
          const response = event.Records[0].cf.response;

          /**
          * This function updates the response status to 200 and generates static
          * body content to return to the viewer in the following scenario:
          * 1. The function is triggered in an origin response
          * 2. The response status from the origin server is an error status code (4xx or 5xx)
          */

          if (response.status >= 400 && response.status <= 599) {
          response.status = 200;
          response.statusDescription = 'OK';
          response.body = 'Body generation example';
          }

          callback(null, response);
          };






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 17 at 12:13









          Alex Malikov

          1516




          1516












          • It works for origin-response trigger, but it does not work for viewer-response, as I mentioned. I want to run my code on each request, use Cloudfront cache and have access to cached object. Now the closest thing I can have is to set cache timeout to 0 and use origin-response trigger.
            – Aliaksei Shytkin
            Nov 20 at 9:26


















          • It works for origin-response trigger, but it does not work for viewer-response, as I mentioned. I want to run my code on each request, use Cloudfront cache and have access to cached object. Now the closest thing I can have is to set cache timeout to 0 and use origin-response trigger.
            – Aliaksei Shytkin
            Nov 20 at 9:26
















          It works for origin-response trigger, but it does not work for viewer-response, as I mentioned. I want to run my code on each request, use Cloudfront cache and have access to cached object. Now the closest thing I can have is to set cache timeout to 0 and use origin-response trigger.
          – Aliaksei Shytkin
          Nov 20 at 9:26




          It works for origin-response trigger, but it does not work for viewer-response, as I mentioned. I want to run my code on each request, use Cloudfront cache and have access to cached object. Now the closest thing I can have is to set cache timeout to 0 and use origin-response trigger.
          – Aliaksei Shytkin
          Nov 20 at 9:26


















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228881%2fhow-can-i-change-status-code-in-viewer-response-cloudfront-event%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          鏡平學校

          ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

          Why https connections are so slow when debugging (stepping over) in Java?