title: How does one handle x-amzn-remapped-authorization when consuming APIs on frontend?
body: <p>While using Laravel Vapor, I encountered my first taste of server-less, in form of a caveat. The <code>authorization</code> header which the API serves to allow the frontend to authenticated is being remapped as <code>x-amzn-remapped-authorization</code>.</p>
  
  <p>This poses a challenge as to at what part of the application should I cleanse this as a lot of the frontend and the underlying authentication packages use the <code>authorization</code> header instead of <code>x-amzn-remapped-authorization</code>. Maybe an axios interceptor can help me cleanse this?</p>
  
  <pre><code>axiosInstance.interceptors.request.use(
    config =&gt; {
      config.headers.authorization = localStorage.getItem("token");
      return config;
    },
    error =&gt; Promise.reject(error)
  );
  </code></pre>