# Connect ME -S and HTTP Authorization: Basic

**URL:** <https://forums.digi.com/t/connect-me-s-and-http-authorization-basic/4290>\
**Category:** Plug N' Play\
**Tags:** customization-pnp\
**Created:** [February 21, 2011, 8:20am UTC](https://forums.digi.com/t/connect-me-s-and-http-authorization-basic/4290 "2011-02-21T08:20:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ptu](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@ptu](https://forums.digi.com/u/ptu)\
**Post date:** [February 21, 2011, 8:20am UTC](https://forums.digi.com/t/connect-me-s-and-http-authorization-basic/4290/1 "2011-02-21T08:20:45Z")

</div>

When I access the /UE/rci URI on the ME, I can use the basic HTTP authorization header, like the following for custom:custom

```auto
Authorization: Basic Y3VzdG9tOmN1c3RvbQ==

```

and the ME respons with “200 OK” status (if the username and password was valid).

However when I try access other objects on the web server, for example /Forms/customization\_file\_upload\_1, this correct authentication is rejected with “401 Unauthorized” status.

Also connectprog.exe first accesses /UE/rci succesfully to test the connection and then fails when trying to access /Forms/customization\_file\_upload\_1.

–\> Connectprog.exe cannot do any upload operation either. What is wrong?

Example:

```auto
&gt;connectprog.exe /info /destip=172.25.1
3.52 /username=root /password=dbps

Digi Connect Programmer
Version 1.6.25.0
Copyright 2003-2009 Digi International Inc.

Connect to device: SUCCESS
Product : Digi Connect ME
Model : Digi Connect ME
MAC : 00:40:9D:31:38:D9
Firmware Version : 2.8.2 (Version 82001116_K 09/16/2008)
Boot Version : 0.0.0.1 (release_82000866_C)
Post Version : 1.1.3 (release_82000867_H)
CPU Utilization : 16%
Uptime : 44 minutes, 36 seconds
Total Memory : 8388608
Used Memory : 4192764
Free Memory : 4195844

&gt;connectprog.exe /upload /destip=172.25
.13.52 /username=custom /password=custom /custom=config.ini

Digi Connect Programmer
Version 1.6.25.0
Copyright 2003-2009 Digi International Inc.

Connect to device: SUCCESS
Upload file config.ini in progress...
    Upload result: FAILED
ERROR: Failed to upload customization file to device:

&gt;

```

(Wireshark shows that connectprog.exe receives 401 response when it tries to upload the file.)

---

<div class="post-metadata">

**Author:** ![charliek](https://avatars.discourse-cdn.com/v4/letter/c/94ad74/32.png) [@charliek](https://forums.digi.com/u/charliek)\
**Post date:** [February 23, 2011, 7:56pm UTC](https://forums.digi.com/t/connect-me-s-and-http-authorization-basic/4290/2 "2011-02-23T19:56:33Z")

</div>

There’s a bug in the K (F6 works) firmware that doesn’t allow you to use Connect Programmer with the module. It has something to do with an authentication check on that page erroneously failing.

---

<div class="post-metadata">

**Author:** ![ptu](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@ptu](https://forums.digi.com/u/ptu)\
**Post date:** [March 8, 2011, 11:43am UTC](https://forums.digi.com/t/connect-me-s-and-http-authorization-basic/4290/3 "2011-03-08T11:43:29Z")

</div>

Thanks for your comment, charliek. Unfortunately I already expected that.

Because of this, we have been doing the file uploads to Digi Connect ME/Wi-ME modules using Internet Explorer controlled via COM automation. Luckily that hack works. Connectprog.exe is used only to discover the module’s IP address, which is then used with IE.