spdy | SPDY daemon and rack adapter | Proxy library

After having developed my application in an unsecured context using HTTP 1.1, I have now deployed it to a HTTP 2 server using HTTPS. All fine and dandy. For 30 seconds... :)

After that, the socket disconnects and connects again. And again. And again.

What I saw missing from the server response are the Connection: keep-alive and Keep-Alive: timeout=5 headers that I get on my HTTP 1.1 server. The code is absolutely identical and communication does work just fine.

I suppose socket.io has some smart way of working over HTTP 2 but I couldn't find anything about this in the documentation.

It's also interesting that the client DOES request the keep-alive header, despite it running on HTTP 2. But alas, nothing is returned and the socket disconnects :(

I noticed somebody tried using SPDY via Express:

Getting socket.io, express & node-http2 to communicate though HTTP/2

I would consider this as a possible solution, but I would like this to work without SPDY as well.

I am using ckEditor with the file browser, filemanager plugin in it. What i am trying to achieve when i configure the CKeditor I am able to browse the file in a certain folder .. but when i try to upload the file through it I am getting an error of 400 Bad Request may be there is something which I need to do ?

Following is my code

I would like to scrape all link for the formation in this website : https://www.formatic-centre.fr/formation/

Apparently the next pages are dynamically loaded with AJAX. I need to simulate those requests using FormRequest from scrapy.

That was I did, I look up for the parameters with developer tools : ajax1

I put those parameters into FormRequest but apparently if it didn't work, I need to include the header, that what I did : ajax2

But it didn't work either.. I'm guessing I'm doing something wrong but what ?

Here's my script, if you want (sorry it's quite long, because I put all the parameters and the headers) :

Recently we've changed over from EC2 to ECS Fargate. Both of these were run through an AWS application balancer. We've run into an issue on one of our endpoints where the JSON is being truncated at random, missing the end of the response, or sometimes it behaves just fine. Interestingly enough the response always has a length of 44149. The response still gives us a 200 either way.

To the best of my knowledge we're trying to use the same PHP and Apache settings on our new system as we did previously. However on the new ECS system we've changed to using PHP-FPM instead of an apache mod.

Versions: PHP-FPM 7.2, Apache 2.4.29

New ECS system truncated response, transferred 42.40 kB (113.36 kB size), headers:

I'm trying to setup Azure Standard CDN on top of another CDN (don't ask) and I have the following rewrite url action to map paths:

It's working but Azure CDN doesn't cache the responses even if I have the second action with an explicit cache override. Query string caching behavior setting in my Azure CDN is set to "Cache every unique URL". What am I missing?

Here is the response headers I get:

The question title is probably not covering the whole subject as I did quite a lot of research and found a number of weird things.

So first of all, what I'm trying to implement is some kind of a client for a website that would work on a user's behalf (not doing anything illegal, just optimizing some of the user's workflow). I've done this for many websites and it worked fine. However, with the current one there's an issue.

Normally, if I encounter a captcha I just open an embedded Chrome window for the user to pass it. However, with the website I'm talking about it doesn't help as the captcha is not displayed in the browser but is sent to me when I'm mimicking the request browser is sending exactly.

So I tried to investigate the difference between the request sent by the Chrome and by my application using Fiddler. However, even requests sent by a real Chrome face the same captcha if I enable the Fiddler.

I've disabled HTTP/2, SPDY and IPv6 in the Chrome as I thought that could be the difference. It didn't help. I've tried comparing the requests sent by Chrome using the Chrome dev tools - there's no difference, both of them are using HTTP/1.1, both have exactly the same headers, exactly the same cookies (or no cookies, it makes no difference). But whenever I enable Fiddler - the website responds with a captcha.

This is the first time I'm encountering something like this and I'm almost ready to bang my head against a wall as I don't see any possible way for the website to understand that the request is being proxied by Fiddler as it's not adding any custom headers or whatever.

Unless the website is somehow detecting the exact way HTTPS connection is being set up which sounds pretty insane... it shouldn't be possible.

Looking for an advice on how to debug this further.

Update:

I didn't find a solution nor did I understand how does the website in question detect direct connections from Chrome, but managed to find a workaround:

I'm taking the page with a captcha that my code receives from the website and substitute the actual page received by the CEF with that captcha page on the fly, thus allowing the user to pass it.

Since it doesn't answer the original question I'm not posting this as an answer and will leave this question open.

I am connected to a server, in Kubernetes cluster, with POST request and headers to upgrade the request. I am using the following function:

After update to angular 9 and universal 9, a got error when i run npm run build:ssr && npm run serve:ssr

I have a server with a REST API that runs on Symfony with API Platform. The GET requests for my resources do not require authorization, however the other operations do. Authorization is handled with a JWT Bearer token.

The client uses React-admin with API Platform Admin. I added this code to send the JWT token along with the operations: