Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
TLMSP curl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CYBER - Cyber Security
TS 103 523 MSP
TLMSP
TLMSP curl
Commits
e33ac6b3
Commit
e33ac6b3
authored
24 years ago
by
Daniel Stenberg
Browse files
Options
Downloads
Patches
Plain Diff
FTP bug fix
new referer magic tricks!
parent
f22717fe
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CHANGES
+20
-0
20 additions, 0 deletions
CHANGES
with
20 additions
and
0 deletions
CHANGES
+
20
−
0
View file @
e33ac6b3
...
...
@@ -6,6 +6,26 @@
History of Changes
Daniel (20 June 2000)
- As Eetu Ojanen suggested, I finally took the step and now libcurl no longer
makes a POST after it has followed a location. When the initial POST has
been done, it'll turned into a GET for the further requests. This is only
interesting when using -L/--location *and* doing a POST at the same time.
While messing with this, I added another weird feature I call 'auto
referer'. If you append ';auto' to the right of a given referer string (or
only use that string as referer), libcurl will automatically set the
previoud URL as refered when it follows a Location: and gets a succeeding
document.
- My hero Rich Gray found the very obscure FTP bug that happened to him only
when passing through a particular firewall and using the PORT command. It
turned out that PORT was the only command in the lib/ftp.c source that
didn't send a proper \r\n sequence but instead used the faulty \n which as
it seemed is supported by most major ftp servers... :-O
Version 7.0.7beta
Daniel (16 June 2000)
- I had avoided this long enough now, so I moved the alternative progress bar
stuff from the lib and added it to the client code. This is now using the
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment