Character limit when creating the Network Resource?

[tmorse305]

Is there a character limit when creating the "Path" for a network resource?  I have a 135 character "path" which adds ok.  I can see the whole path but when I test it I get a 403 error.  If I take the whole url and paste it into a browser it works fine.  I have lots of network resources configured that work fine but nothing close to the length of this one.

This is the url:

https://www.virtualsmarthome.xyz/url_routine_trigger/activate.php?trigger=023dfc97-3d2e-4c32-a3e2-b8ee5c0e7ca9&token=af23886c-91a9-4b84-****-1541bc9237b9&response=html

I have it set to https, POST, Port 443, Timeout 10000, Mode: URL-Encoded

I've tried C Escaped but same result

I've tried the 2 check boxes but no luck there either.

Thanks for any advice.

 

Update:

I've confirmed that the entire url is being sent by eisy, using Wireshark, so that's not the issue. 

 

Edited Tuesday at 09:07 PM by tmorse305

[larryllix]

21 hours ago, tmorse305 said:

Is there a character limit when creating the "Path" for a network resource?  I have a 135 character "path" which adds ok.  I can see the whole path but when I test it I get a 403 error.  If I take the whole url and paste it into a browser it works fine.  I have lots of network resources configured that work fine but nothing close to the length of this one.

This is the url:

https://www.virtualsmarthome.xyz/url_routine_trigger/activate.php?trigger=023dfc97-3d2e-4c32-a3e2-b8ee5c0e7ca9&token=af23886c-91a9-4b84-****-1541bc9237b9&response=html

I have it set to https, POST, Port 443, Timeout 10000, Mode: URL-Encoded

I've tried C Escaped but same result

I've tried the 2 check boxes but no luck there either.

Thanks for any advice.

 

Update:

I've confirmed that the entire url is being sent by eisy, using Wireshark, so that's not the issue. 

 

REST commands use GET, not POST. This may depend on what device you are talking to though.

Edited Tuesday at 09:59 PM by larryllix

[kclenden]

On 9/8/2025 at 8:00 PM, tmorse305 said:

I can see the whole path but when I test it I get a 403 error.

A 403 error generally means that the server has received your command but has decided that you're not authorized to execute that command.  So unless the URL that you're trying to use includes credentials (and they're being cutoff because the URL is too long), I don't think the problem is the length of your URL, but instead that you must first authenticate so that the server knows your are authorized.

This is from the virtualsmarthome.xyz website:

Since you have an URL, I'm assuming that you've completed steps 1 & 2, but have you also done steps 3 & 4?  I have absolutely no experience with Alexa skills, nor virtualsmarthome.xyz, so I'm just shooting in the dark in case any of this triggers (all puns intended) something in your mind.

Edited Wednesday at 06:29 AM by kclenden
Added steps from virtualsmarthome.xyz website

[tmorse305]

Thanks for your replies, I opened a ticket, and Michel quickly identified the problem:

"It (the Virtual Server) does not accept http 1.1. It's expecting http2 which Network resources do not support."

Thanks to Michel for the great support!

[kclenden]

7 hours ago, tmorse305 said:

"It (the Virtual Server) does not accept http 1.1. It's expecting http2 which Network resources do not support."

Interestingly our robot overlords do not agree:

Now mind you, I trust Michel more than any AI, but maybe he meant HTTPS vs HTTP as opposed to HTTP2 versus HTTP1.1?

[larryllix]

2 hours ago, kclenden said:

Interestingly our robot overlords do not agree:

Now mind you, I trust Michel more than any AI, but maybe he meant HTTPS vs HTTP as opposed to HTTP2 versus HTTP1.1?

Who would write an http: driver that isn't backward compatible with the accepted protocol for what 20 years? Very weird for such a new protocol standard.

[tmorse305]

21 hours ago, larryllix said:

Who would write an http: driver that isn't backward compatible with the accepted protocol for what 20 years?

Turns out, not VirtualSmartHome.

I just had the same problem when I tried to code this into a plugin.  The issue was the headers not whether it was HTTP/1.1 or HTTP/2.  With the proper headers it works with either one.  POST or GET also work.

Edited Thursday at 09:12 PM by tmorse305