Hi,
I'm using your JSCompressor API (https://jscompressor.treblereel.dev/compile) to compile JavaScript code. When I send a very small payload (e.g., "var a = 1;"), the API works as expected. However, when I try to compile a larger payload—approximately 1.74 MB in size (generated from concatenating Blockly source files)—the request fails with an SSL error.
The error I receive is:
HTTPSConnectionPool(host='jscompressor.treblereel.dev', port=443): Max retries exceeded with url: /compile (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:2406)')))
It appears that the connection is being terminated during the TLS negotiation when a large payload is sent. This leads me to wonder if there might be a limit on the payload size or if there are certain TLS settings on the server that could be causing this issue.
Could you please advise on the following?
Is there a maximum payload size that the API supports?
Are there any known issues or recommended settings when dealing with large payloads?
Would you consider increasing the limit or providing guidelines for handling large files?
Any assistance or guidance would be greatly appreciated.
Thank you for your work on this API!
Best regards,
Hi,
I'm using your JSCompressor API (https://jscompressor.treblereel.dev/compile) to compile JavaScript code. When I send a very small payload (e.g., "var a = 1;"), the API works as expected. However, when I try to compile a larger payload—approximately 1.74 MB in size (generated from concatenating Blockly source files)—the request fails with an SSL error.
The error I receive is:
HTTPSConnectionPool(host='jscompressor.treblereel.dev', port=443): Max retries exceeded with url: /compile (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:2406)')))
It appears that the connection is being terminated during the TLS negotiation when a large payload is sent. This leads me to wonder if there might be a limit on the payload size or if there are certain TLS settings on the server that could be causing this issue.
Could you please advise on the following?
Is there a maximum payload size that the API supports?
Are there any known issues or recommended settings when dealing with large payloads?
Would you consider increasing the limit or providing guidelines for handling large files?
Any assistance or guidance would be greatly appreciated.
Thank you for your work on this API!
Best regards,