CORS when connecting to self-hosted gitlab

jen · July 11, 2020, 10:17pm

Hey @AnaTofuZ,
The best fix would be to add the “Access-Control-Allow-Origin” header on the Gitlab side, to enable your origin (https://ie.u-ryukyu.ac.jp) to access it. We don’t know the answer to whether that’s possible but Gitlab support should!

If it turns out to not be possible to add that header, I’d suggest reviewing this article about proxying your requests through a Netlify Function:

Here is the function you’ll call from your page:

github.com

netlify/cli/blob/a0160b1b98352914b3818af891c5f8ae15cf4db6/src/functions-templates/js/node-fetch/node-fetch.js

/* eslint-disable */
const fetch = require("node-fetch");
exports.handler = async function(event, context) {
  try {
    const response = await fetch("https://icanhazdadjoke.com", {
      headers: { Accept: "application/json" }
    });
    if (!response.ok) {
      // NOT res.status >= 200 && res.status < 300
      return { statusCode: response.status, body: response.statusText };
    }
    const data = await response.json();

    return {
      statusCode: 200,
      body: JSON.stringify({ msg: data.joke })
    };
  } catch (err) {
    console.log(err); // output to netlify function log
    return {

This file has been truncated. show original

Let us know if this helps or if you have additional questions!