Skip to content
Snippets Groups Projects
  1. Sep 16, 2004
  2. Sep 10, 2004
    • Daniel Stenberg's avatar
      - Bug report #1025986. When following a Location: with a custom Host: header · b8b56248
      Daniel Stenberg authored
        replacement, curl only replaced the Host: header on the initial request
        and didn't replace it on the following ones. This resulted in requests with
        two Host: headers.
      
        Now, curl checks if the location is on the same host as the initial request
        and then continues to replace the Host: header. And when it moves to another
        host, it doesn't replace the Host: header but it also doesn't make the
        second Host: header get used in the request.
      
        This change is verified by the two new test cases 184 and 185.
      b8b56248
  3. Jul 04, 2004
  4. Jul 01, 2004
  5. Jun 24, 2004
  6. Jun 16, 2004
  7. Jun 15, 2004
  8. Jun 03, 2004
  9. May 26, 2004
  10. May 25, 2004
  11. May 24, 2004
  12. May 17, 2004
  13. May 12, 2004
  14. May 07, 2004
  15. May 04, 2004
  16. Apr 29, 2004
  17. Apr 27, 2004
  18. Apr 26, 2004
  19. Apr 22, 2004
  20. Apr 21, 2004
    • Daniel Stenberg's avatar
      Fix the "lingering close" problem when re-using a connection, as test case · 1401d909
      Daniel Stenberg authored
      160 shows.
      
      We got no data and we attempted to re-use a connection. This might happen if
      the connection was left alive when we were done using it before, but that was
      closed when we wanted to read from it again. Bad luck. Retry the same request
      on a fresh connect!
      
      Deleted the sockerror variable again, it serves no purpose anymore.
      1401d909
  21. Apr 20, 2004
  22. Apr 15, 2004
  23. Apr 13, 2004
  24. Apr 07, 2004
  25. Apr 06, 2004
  26. Mar 30, 2004
  27. Mar 25, 2004
  28. Mar 24, 2004
  29. Mar 23, 2004
  30. Mar 12, 2004
  31. Mar 11, 2004
  32. Mar 10, 2004
  33. Mar 09, 2004
  34. Mar 03, 2004
Loading