They are giving response codes like 403 so it's not a failure to resolve and I agree it's not DNS... It's behaving differently based on different sub pages so it's something underneath the https encryption. Maybe an intermediary WAF that decrypts? Maybe some weird server side tooling that has govt provided?

I would guess WAF but I'd love to hear from someone who actually knows.

Brkdncr@lemmy.world · 14 pts · 273d

It’s either

Client side ssl forward proxy (MitM cert installed on client)
in-line decryption in the server
client side software
tls downgrade
cert authority compromise

baltakatei@sopuli.xyz · 12 pts · 273d

Right? If it were an unencrypted HTTP GET request, then every router on the way would see the plaintext string boobs in the URL and therefore intercept it.

If I had to guess, Iran has so few landline connections that they man-in-the-middle every TLS connection they can by either forcing every server to hand over their private key files (difficult) or by forcing a certificate authority trusted by default Web browsers (there's a lot of them) to issue certificates for every top level domain they see in SNI data attached to encrypted packet headers; the latter method need not even require participation by Iranian servers, so long as the traffic is bottlenecked for man-in-the-middle attacks and outsiders don't question unusual certificate authorities being used.

SchwertImStein@lemmy.dbzer0.com · 32 pts · 273d (14 replies)

fishos@lemmy.world · -5 pts · 272d (13 replies)

[ removed ]

W3dd1e@lemmy.zip · 10 pts · 272d (3 replies)

To keep me off Twitter, thank god.

fishos@lemmy.world · -1 pts · 271d (2 replies)

[ removed ]

SlurpingPus@lemmy.world · 3 pts · 271d

Lemmy itself doesn't allow posting a link and an image together, at least not in the default UI on lemmy.world. Consequently, apps being able to show them together isn't the go-to expectation.

P.S. Upon reading your comments further below, it's outstanding what an annoying prick you are.

W3dd1e@lemmy.zip · 2 pts · 271d

I was thinking maybe some types of Lemmy apps/clients don’t show it? Mine does but I was giving the commenter the benefit of the doubt.

Once I was trying to find info on my server’s administration policies and including time it. Turns out it wasn’t available in my app at the time, I had to go to the website.

GlenRambo@jlai.lu · 7 pts · 272d (8 replies)

Saves a click?

I dont see a screenshot.

SchwertImStein@lemmy.dbzer0.com · 6 pts · 272d

exactly, there is no screenshot and I don't want anyone to need to go to the website

fishos@lemmy.world · -15 pts · 272d (6 replies)

[ removed ]

SchwertImStein@lemmy.dbzer0.com · 8 pts · 272d (5 replies)

I'd rather my app didn't interact with twitter without my permission

fishos@lemmy.world · -18 pts · 272d (4 replies)

[ removed ]

SchwertImStein@lemmy.dbzer0.com · 7 pts · 272d (3 replies)

Hmm, Voyager seems to have a problem with posts that are cross-post and have a photo. Thanks for pointing that out.

fishos@lemmy.world · -12 pts · 271d

[ removed ]

mirshafie@europe.pub · 11 pts · 272d

It was annoying as hell trying to download a LaTeX compiler and having the entire word be blocked, presumably because certain degenerates use latex - the material - for immoral acts.

MadnessForTsar@lemmy.world · 11 pts · 273d (8 replies)

Why with Iran?

sundray@lemmus.org · 44 pts · 273d (6 replies)

Presumably because instead of responding to the request for boobs.jpg with with an HTTP 404 error (meaning, "not found"), Iran's censorship tech returns a 403 error (meaning basically "you are forbidden from accessing this resource).

The "boobs" are "forbidden" you see; the tech mirrors the ruling party's moral stance, probably coincidentally. Trying the same curl command in Russia and China will likely just get you a 404 error, so the joke really only works with Iranian servers. The 404 version is slightly less funny: "We couldn't find the boobs!"

fahfahfahfah@lemmy.billiam.net · 15 pts · 273d

Hey, at least they’re using HTTP codes correctly.

murmelade@lemmy.ml · 9 pts · 273d (3 replies)

They should change it to 80085 error.

otp@sh.itjust.works · 2 pts · 272d (2 replies)

Browsers don't know how to handle 80085

n7gifmdn@lemmy.ca · 2 pts · 261d (1 reply)

Either do most men now-a-days.

otp@sh.itjust.works · 2 pts · 261d

Hah! That's what she said. Poor her.

mirshafie@europe.pub · 7 pts · 272d

It's 403 because they are upfront about the resource being censored as opposed to unavailable, and they tell you who to contact if you have legigimate reasons to access it.

SlurpingPus@lemmy.world · 3 pts · 271d

Overwhelming majority of countries don't do keyword-based blocking, especially not for incoming requests.

MissingInteger@lemmy.zip · 9 pts · 272d (1 reply)

curl -i https://irangov.ir/boobs.jpg # HTTP 200
curl -i https://president.ir/boobs.jpg # HTTP 200
curl -i https://divar.ir/boobs.jpg # HTTP 404

Can't reproduce. The goverment websites don't even handle the error correctly: they give a HTTP 200 and an error page.

Does anyone have an actual working example?

Buddahriffic@lemmy.world · 2 pts · 270d

Lol when I first read your screenshot, I thought for a moment they actually served you boobs.jpg from the government and president sites.

But maybe this is disinformation to make people think servers in Iran aren't?

"Oh boobs.jpg just gives a 404, can't be in Iran!" (When the server is in Iran)

Buddy doesn't even say what domain they figured out was in Iran with this "trick".

technocrit@lemmy.dbzer0.com · 8 pts · 272d

First they came for the boobs...