Home > ant task, apache ant, http, java, web services, xml > apache ant http task 1.1.3 released

apache ant http task 1.1.3 released

I’ve released the missing link apache ant http task version 1.1.3.  This is mainly a bugfix and enhancement release.

I would like to thank everyone who contributed by logging issues on the google code project!  I utilized some of the patches that people have submitted.

The issues fixed for 1.1.3 can be seen here, which include the following:

  • Make the task less verbose by default, now utilizes ant log levels (can use -verbose switch to get back original logging)
  • Skip a HTTP request if writing to an outFile and new “update” attribute is set to false (user submitted patch)
  • Added an attribute “statusProperty” to save the response http status code to a property
  • Added an attribute “entityProperty” to save the response http entity to a property
  • Added an attribute “value” to the entity node which allows you to use an arbitrary value (including ant properties) as the request entity
  • Fixed a bug where writing to an outFile did not create the parent directories (user submitted patch)

Again, I would like to thank everyone for their feedback and patch submissions.

Please give me any other feedback, bug reports and or feature requests that you may have!


  1. Oli
    September 20, 2011 at 7:25 am

    Hi Alex,

    thanks for your ant-http tasks, works great!

    Have you uploaded also the artifact into a Maven Repository? I couldn’t find anything.


  2. David Scott
    July 13, 2012 at 4:43 pm

    This task is very useful, but I can’t get file uploading to work. Can you please provide an example of how to do this? The readme PDF does not show how to do a file upload.

    • Alex
      July 13, 2012 at 4:45 pm

      HI David,

      Page 6 of the readme.pdf shows an example of this, you nest an entity node inside and can set the “file” attribute to a file. You can set binary=true as well if necessary

      • David Scott
        July 13, 2012 at 6:01 pm

        I was confused that “entity” referred to the file to be uploaded, so I did not recognize this in the documentation. I tried that example, but it did not work for me. Maybe my server (Adobe CQ) is expecting a different format for the post.

  3. Alex
    July 13, 2012 at 6:07 pm

    Hi David,

    The adobe products often lock down and expect very specific headers around file uploads (this is at least true for Flash Player related uploads), For example, check the flash player livedocs of how Flash Player formats a file upload:


    I would imagine that in your case, the reverse would be true, where your Adobe server is accepting a request conforming to a certain format (method, headers, etc), but I’ve never used Adobe CQ myself.

    If this turns out to be the case, you could try using the XML element to specify custom headers in your request to make the server happy

    • David Scott
      July 13, 2012 at 6:32 pm

      Thanks for the info. I’ve already spent much of the day trying different things, but I think it’s time to give up and just use cURL (which I already got working, but didn’t want to use because I did not want to add another dependency). I would not be surprised if the CQ documentation is incorrect about what their server actually expects in the upload request.

  4. October 22, 2015 at 10:55 am

    Hi Alex, many thanks for your ant http task library – are you still maintaining this?

    Google code has now gone into read-only mode, and I was wondering if you had any plans to migrate it to another code hosting service (github, bitbucket, etc.)…. I’ve migrated my open source projects, and would be happy to help you migrate…


    • Alex
      October 22, 2015 at 11:51 am

      I’m not currently maintaining this project, but I just ran the google code -> GitHub exporter, the exported project is here: https://github.com/alex-sherwin/missing-link/

      If you’re still using this and want to maintain it, please feel free to fork is and do whatever you please to it.

      Let me know and I’ll put a note in the README.md on the GitHub project to the new/maintained fork


  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: