u/CharityAdmirable8774

Hi everyone,

I’m experimenting with a very restricted JavaScript execution environment where the following characters are blocked:

/  $  %  )  {  }  '  <

Outbound requests still seem to work in some situations, but handling or forwarding response data becomes difficult because many common syntax patterns are unavailable.

I’m curious about which browser mechanisms, events, properties, or built-in behaviors can still interact with external resources in constrained environments like this.

I’m mainly trying to better understand browser parsing and execution behavior under unusual restrictions.

Thanks.

Hi everyone,

I’m researching restricted JavaScript execution contexts and I’m curious about browser behavior when several characters are filtered.

For example, these characters are blocked:
/ $ % ) { } ' <

Because of that, common patterns like fetch().then() cannot be used.

I can still make requests to external endpoints, but I’m unable to read the response data or send the retrieved data elsewhere due to the character restrictions.

In general, are there JavaScript properties, events, or browser features that can still interact with external resources or handle response data in heavily filtered environments like this?

I’m mainly trying to understand browser behavior and limitations in restricted contexts.

Thanks.