Skip to content
  • Hjem
  • Seneste
  • Etiketter
  • Populære
  • Verden
  • Bruger
  • Grupper
Temaer
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Kollaps
FARVEL BIG TECH
  1. Forside
  2. Ikke-kategoriseret
  3. Pleroma Webfinger compatibility

Pleroma Webfinger compatibility

Planlagt Fastgjort Låst Flyttet Ikke-kategoriseret
activitypubpleromawebfinger
10 Indlæg 3 Posters 0 Visninger
  • Ældste til nyeste
  • Nyeste til ældste
  • Most Votes
Svar
  • Svar som emne
Login for at svare
Denne tråd er blevet slettet. Kun brugere med emne behandlings privilegier kan se den.
  • julian@community.nodebb.orgJ This user is from outside of this forum
    julian@community.nodebb.orgJ This user is from outside of this forum
    julian@community.nodebb.org
    wrote sidst redigeret af
    #1

    Does anybody know what exactly Pleroma needs for a valid Webfinger check? I’m attempting to figure out why @jmtd@pleroma.debian.social won’t resolve in NodeBB, and it’s because the webfinger call returns 400 Bad Request.

    NodeBB is calling https://pleroma.debian.social/.well-known/webfinger?resource=acct%3Ajmtd%40pleroma.debian.social with User-Agent and Content-Type headers (curiously, it’s not sending Accept, but it also fails if that header is set, so that’s irrelevant.)

    Navigating to that webfinger url in the browser returns XML, which is 😬 but I’m not even getting that when NodeBB makes the call.

    1 Reply Last reply
    1
    0
    • activitypub@community.nodebb.orgA activitypub@community.nodebb.org shared this topic
      nodebb@fosstodon.orgN nodebb@fosstodon.org shared this topic
    • thisismissem@hachyderm.ioT This user is from outside of this forum
      thisismissem@hachyderm.ioT This user is from outside of this forum
      thisismissem@hachyderm.io
      wrote sidst redigeret af
      #2

      @julian fedify manages it, so many take a look at their webfinger implementation?

      1 Reply Last reply
      0
      • thisismissem@hachyderm.ioT This user is from outside of this forum
        thisismissem@hachyderm.ioT This user is from outside of this forum
        thisismissem@hachyderm.io
        wrote sidst redigeret af
        #3

        @julian try sending `Accept: application/jrd+json`

        Since that's the content-type for webfinger, not application/json. In fedify, the fetch call is also with redirect manual, such that max redirection logic and SSRF checks can be done.

        1 Reply Last reply
        0
        • thisismissem@hachyderm.ioT This user is from outside of this forum
          thisismissem@hachyderm.ioT This user is from outside of this forum
          thisismissem@hachyderm.io
          wrote sidst redigeret af
          #4

          @julian oh! it's because you're sending the Content-Type header, send Accept instead.

          thisismissem@hachyderm.ioT 1 Reply Last reply
          0
          • thisismissem@hachyderm.ioT thisismissem@hachyderm.io

            @julian oh! it's because you're sending the Content-Type header, send Accept instead.

            thisismissem@hachyderm.ioT This user is from outside of this forum
            thisismissem@hachyderm.ioT This user is from outside of this forum
            thisismissem@hachyderm.io
            wrote sidst redigeret af
            #5

            @julian which actually makes sense, because with a GET request, you're not sending any request content, and Content-Type applies to the request body, not to the content type you want back.

            julian@community.nodebb.orgJ 1 Reply Last reply
            0
            • thisismissem@hachyderm.ioT thisismissem@hachyderm.io

              @julian which actually makes sense, because with a GET request, you're not sending any request content, and Content-Type applies to the request body, not to the content type you want back.

              julian@community.nodebb.orgJ This user is from outside of this forum
              julian@community.nodebb.orgJ This user is from outside of this forum
              julian@community.nodebb.org
              wrote sidst redigeret af
              #6

              thisismissem@hachyderm.io yeah, I tried sending Accept too, which also fails. Will try the suggested type.

              The library we use just blanket sends content-type because we’re usually POSTing haha. Shouldn’t hurt to include it, but who knows.

              1 Reply Last reply
              0
              • thisismissem@hachyderm.ioT This user is from outside of this forum
                thisismissem@hachyderm.ioT This user is from outside of this forum
                thisismissem@hachyderm.io
                wrote sidst redigeret af
                #7

                @julian eh? I mean, sure, or just detect whether the request is a GET / HEAD / OPTIONS request, and then don't send the content-type header? (since those methods don't support request bodies iirc)

                julian@community.nodebb.orgJ 1 Reply Last reply
                0
                • thisismissem@hachyderm.ioT thisismissem@hachyderm.io

                  @julian eh? I mean, sure, or just detect whether the request is a GET / HEAD / OPTIONS request, and then don't send the content-type header? (since those methods don't support request bodies iirc)

                  julian@community.nodebb.orgJ This user is from outside of this forum
                  julian@community.nodebb.orgJ This user is from outside of this forum
                  julian@community.nodebb.org
                  wrote sidst redigeret af
                  #8

                  thisismissem@hachyderm.io yes, but… that takes effforrrrrrrtttt 😦

                  Anyway, ding ding ding, application/jrd+json was it 🏆

                  1 Reply Last reply
                  0
                  • trwnh@mastodon.socialT This user is from outside of this forum
                    trwnh@mastodon.socialT This user is from outside of this forum
                    trwnh@mastodon.social
                    wrote sidst redigeret af
                    #9

                    @julian are you sending accept application/json or accept application/jrd+json instead of accept application/activity+json?

                    julian@community.nodebb.orgJ 1 Reply Last reply
                    0
                    • trwnh@mastodon.socialT trwnh@mastodon.social

                      @julian are you sending accept application/json or accept application/jrd+json instead of accept application/activity+json?

                      julian@community.nodebb.orgJ This user is from outside of this forum
                      julian@community.nodebb.orgJ This user is from outside of this forum
                      julian@community.nodebb.org
                      wrote sidst redigeret af julian@community.nodebb.org
                      #10

                      trwnh@mastodon.social before, I was not sending Accept at all, now I am sending application/jrd+json.

                      1 Reply Last reply
                      1
                      0
                      Svar
                      • Svar som emne
                      Login for at svare
                      • Ældste til nyeste
                      • Nyeste til ældste
                      • Most Votes


                      • Log ind

                      • Har du ikke en konto? Tilmeld

                      • Login or register to search.
                      Powered by NodeBB Contributors
                      Graciously hosted by data.coop
                      • First post
                        Last post
                      0
                      • Hjem
                      • Seneste
                      • Etiketter
                      • Populære
                      • Verden
                      • Bruger
                      • Grupper