13
Proxy image urls get mangled (slrpnk.net)
submitted 2 months ago by to c/boostforlemmy@lemmy.world
7 comments fedilink hide all child comments
 

Is this a boost bug perhaps? What injects this proxy part? slrpnk.net admin said they think it's a client bug so here I am

Note the hhttps (double h) and the missing h further after the proxy ttps

all 7 comments

sorted by: hot top controversial new old
[โ€“] 2 points 2 months ago (1 child)

Where's the images hosted on slrpnk.net or the site in the mangles URLs (which I can't see now, while typing this)?

Because if you didn't mean to link to images on slrpnk.net, then I have a hard time believing it's not something misconfigured on slrpnk.net.

Otherwise why should you get that specific string added? Sure, if it had just been the site part, maybe it could be boost, but I'd still doubt it. But the extra path? That's some kind of proxy module the admin has installed and forgot about.

How does other posts, by other users on your in instance, with image links look?

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [โ€“] [S] 1 point 2 months ago

    I guess that's what I'm asking, is the proxy a default lemmy feature or my instance's specific implementation? Could it be a boost thing? There's so many options and I don't really understand enough about this to really reason about it

  • permalink
  • fedilink
  • source
  • parent
    • [โ€“] 2 points 2 months ago (3 children)

    Have seen this, too. Once. With boost. No developer in here, don't expect a solution.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [โ€“] 2 points 2 months ago (2 children)

    Oh shit, did the dev peace out?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    • [โ€“] [S] 1 point 2 months ago

    Interestingly I just saw it happen in another post: https://lemdro.id/post/lemdro.id/45613195 the bottommost image link has the double hhttps, which is silly because the other images are fine, but this probably proves it's not my client as I could reproduce in an incognito browser. It does seem to be quokk.au links in both cases? But why would proxies choke on that specifically?

  • permalink
  • fedilink
  • source
    •