Relative API Endpoint

[IgorKha]

Environment

------------------------------
- Operating System: Darwin
- Node Version:     v20.9.0
- Nuxt Version:     3.12.4
- CLI Version:      3.12.0
- Nitro Version:    2.9.7
- Package Manager:  [email protected]
- Builder:          -
- User Config:      devtools, modules, pinia, runtimeConfig, graphql-client, nitro, ssr, routeRules, ui, colorMode, components, compatibilityDate
- Runtime Modules:  @pinia/[email protected], [email protected], @pinia-plugin-persistedstate/[email protected], @nuxt/[email protected]
- Build Modules:    -
------------------------------

import { existsSync } from 'fs'

const schemaPath = './schema.graphql'
const schema = existsSync(schemaPath) ? schemaPath : undefined

export default defineNuxtConfig({
  modules: [
    'nuxt-graphql-client',
    ...
  ]
...
  'graphql-client': {
      clients: {
        default: {
          host: '/api/gql',
          schema
        },
      },
    },

  nitro: {
    routeRules: {
      '/api/gql': { proxy: 'http://127.0.0.1:4000/api/gql' },
    }
  },

...

Describe the bug

Hi, I'm not sure if this is a bug, but if not, I need some help understanding what's happening. I want to make my API endpoint relative because I don't have a static hostname on my devices, and it can change depending on the IP assigned to the device.

1. When proxying through Nitro with host: '/api/gql' (calling the API via frontend proxying), I receive responses in Insomnia. This leads me to believe that such an approach works.
2. However, when I try to use nuxt-graphql-client on the frontend, I don't see any requests in the browser at all.
3. In the same scenario as point 2, but using host: 'http://192.168.1.10:4000/api/gql' (hardcoding the backend's IP and port), everything works fine.

Expected behaviour

I expect relative paths to work the same way as full paths.

Thank you!

Reproduction

No response

Additional context

No response

Logs

No response