-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PUT Requests are timing out at spoa-mirror agent. #18
Comments
Hello there.. Has anyone else there hit this issue. POST and GETs are working, however i have PUT requests that need to service and i get the Timeout as well. on my side im using https in the --mirrorurl but i dont think it makes a difference since POSTs are working (however the upstream call is a PUT not a POST server). Some information haproxy.cfg bits: mirror This is in my https-in frontend: #--------------------------------------------------------------------- Mirror.conf spoe-message mirror Any tips would be great to get PUT working |
Best tip : if you look at the source code, this project is using haproxy SPOE protocol and curl libraries. It's not rocket science. |
Hello all, as for the PUT HTTP method, it could be added. If you want you can look at the following url https://github.com/RallySoftware/spoa-mirror/tree/empty-put-body where the user @argreway solved it for himself. The patch is very simple, I just need to have more time for this project because I have some other commitments. Best regards. |
Hey there.. @baylanger - so friendly.. i had started to look at the code, and had spent a bit of time today, noticed that there was some work and a issue being done and added... sorry for asking.. I do have it working very nicely with POST/GET... @zaga00 - thanks for the link.. ill take a stab it .. |
Hey there. Amazing.. i will try it out right now .. thanks so much! |
Hello @zaga00 this works great now, thanks alot. A question for you.. if now i want to change parts of the frame body (specifically the HTTP Header parts encapsulated - i.e. (a) - can i do this with a set var in the spoe section, something like set var arg8:Host:"my.new.host.com"? the end goal is really to have a mirror spillter that allows me to change the HTTP header and body parts on the way "out" to the second (or multiple) destinations (like goduplicator ). the PUT option works great and thanks for this!, I can see that the HOST and SNI from the original call is kept (as a mirror would expect) rather than rewrite with the --mirrorurl. I am working towards a method of being able to split /mirror and alter just a couple header aspects. Any inputs/thoughts would be appreciated. |
Just a note - for this issue - the problem for me is solved - any other notes are about "extended/new features" - but the PUT timeout issue is resolved (tested at 1200/tx/sec and it was stable). |
Hello @lmcdasm, HTTP headers are sent via SPOP and added to the hdrs list of the mirror structure in the spoa_msg_arg_hdrs() function. cURL sets HHTP headers using that list in the mir_curl_set_headers() function. In one of these two functions, the recognition and replacement of certain HTTP headers can be added. For some other simpler way I don't know, possibly something can be tried via fetching HAProxy samples so that instead of req.hdrs_bin in the SPOA configuration something more complex and complicated can be used. Best regards. |
Thanks again @zaga00 you have helped me alot and appreciate your input! Cheers |
We noticed that PUT requests are timing out at spoa-mirror agent. GET, POST are working fine in our setup as expected. Based on your Readme doc, its mentioning below lines under "Know Bugs & Limitations". Can you provide some instructions or any document references - how to add PUT request support also in spoe-mirror agent?
Appreciate your help in advance. Thanks
Text From Your Readme -
"HTTP methods that certainly work are GET, HEAD and POST. Other methods can be
added if necessary"
Sample PUT request from our SPOE-Mirror logs for your reference -
The text was updated successfully, but these errors were encountered: