Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Support for URL rewriting under IIS7

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • waldhorn
    replied
    Re: Support for URL rewriting under IIS7

    From a related thread today, Alpha will soon allow overriding the response code in custom error pages.

    Originally posted by Lenny Forziati View Post
    You will be able to do this by setting Response.StatusCode and Response.StatusDescription as of the next prerelease. The server was inadvertently overwriting any value you may set in a custom error page and that has now been fixed.
    With that, one should now be able to use the custom 404 error page to deploy a basic URL rewrite engine, server-wide, and still display the desired response code. While this may not be as elegant a solution as employing a dedicated rewrite module (as found Apache, IIS, etc.), it should serve in the interim until Alpha's transition to IIS.

    Leave a comment:


  • kkfin
    replied
    Re: Support for URL rewriting under IIS7

    In fact seems like you are right. I tested earlier using response.redirect with full path and that makes the fully page name also in URL.
    Let say you have url http://localhost/test. You can cheat Alpha creating test folder under root and then put index.a5w in that folder. All the code and html is then in this file. Then you get normal 200 ok response and the url seems to remain nice. This seems to also work with links and also with response.redirect("http://localhost/test").

    I just tested in localhost.

    Leave a comment:


  • waldhorn
    replied
    Re: Support for URL rewriting under IIS7

    Originally posted by kkfin View Post
    As I explained if you don't give Was page extension it understand request as a folder name and you can't change this behavior.
    Hi Ken. Thank you for your ongoing discussion. In my experimentation, it appears that WAS understands and records the full request, including missing folders and sub-folders, and assigns it to the property Request.Script_Name. (See wiki entry on Request Object.)

    So, going back to the method that I outlined above, let's say that we've set up 404-processing.a5w in the application server's configuration to process 404 errors. And, in that file we write
    Code:
    <p>Request.Script_Name: <%a5 ? Request.Script_Name %></p>
    Now, if we browse to mydomain.com/non-existent-sub-folder-1/non-existent-sub-folder-2/ , WAS--unable to locate these phantom folders--hands off the request to 404-processing.a5w which then processes our request and, voil�, successfully returns the following to our browser:
    Request.Script_Name: /non-existent-sub-folder-1/non-existent-sub-folder-2/

    Meanwhile, the browser continues to display our 'friendly' URL. All that is left is to code a method for parsing the results of Request.Script_Name for further dynamic processing by our application.

    I've tried it out, and it does appear to work as expected. However, I still haven't figured out how to override the undesired header response of "404 - Not Found" and change it to the search-engine-friendly "200 - OK". I tried Response.StatusCode = 200 and Response.StatusDescription = "OK" (see discussion here), but they are ignored by WAS when processing a 404 error. Perhaps there's a way...or we may just need to wait for a more elegant solution in the upcoming release of Alpha's IIS module.

    Best,

    Mark

    Leave a comment:


  • kkfin
    replied
    Re: Support for URL rewriting under IIS7

    Originally posted by waldhorn View Post
    Theoretically, you would do the following:
    • Create a processing A5W page. It's job would be to parse out the (bogus/non-existent) requested path and return whatever dynamic content you like.
    • Assign the 404 "not found" error page (under Web Project Control Panel > View > Application Server > Errors Tab) to the published location of the A5W page created above.
    As I explained if you don't give Was page extension it understand request as a folder name and you can't change this behavior. You can process this request easily but Was always seeks the default pages listed in server configuration and the response url you give will have to have full page name and needed query strings so no nice urls at all. So this is not possible even in theory.

    Normally with nice urls the nice url points in fact to a function and the function process the request to the "right url". This is not possible in Alpha.

    If you run Was behind reverse proxy then you can have nice urls of course.

    Leave a comment:


  • waldhorn
    replied
    Re: Support for URL rewriting under IIS7

    Originally posted by frankbicknell View Post
    After looking at the rewrite descriptions, Although I don't know the exact procedure I feel confident that you could create your own 'rewrite module' within Alpha5 now.
    Yes, and no.

    Originally posted by kkfin View Post
    So how you bypass this behavior within Alpha5 now? I don't feel confident at all this is possible now.
    Theoretically, you would do the following:
    • Create a processing A5W page. It's job would be to parse out the (bogus/non-existent) requested path and return whatever dynamic content you like.
    • Assign the 404 "not found" error page (under Web Project Control Panel > View > Application Server > Errors Tab) to the published location of the A5W page created above.

    The interaction process would go like this:
    • User browses to your 'pretty URL' (e.g., mydomain.com/your-non-existent-sub-directory-1/your-non-existent-sub-directory-2/)
    • The web application server ("WAS") processes the request and finds that it can't locate the requested file/directory.
    • WAS calls up the 404 error page that you created.
    • The 404 error page parses out the components of the URL and displays your desired dynamic content.

    Caveat: It appears that, once WAS calls up the 404 error, one can't change the header response code and description via X-Basic from "404 - Not Found" to "200 - OK". This is an issue because sending a 404 response code to search engines would be the kiss of death to your public web pages. They would eventually just drop out of search indexes.

    So, unless Alpha is willing to modify this behavior in the near future, we may need to wait for Alpha to complete their transition from Alpha's WAS to Microsoft's IIS before getting URL rewriting. As I noted in my earlier posts, Microsoft's IIS is currently capable of gracefully handling URL rewriting. Fingers crossed.

    Leave a comment:


  • kkfin
    replied
    Re: Support for URL rewriting under IIS7

    Originally posted by frankbicknell View Post
    After looking at the rewrite descriptions, Although I don't know the exact procedure I feel confident that you could create your own 'rewrite module' within Alpha5 now.
    If your URL is http:/localhost/test then Was will search a subfolder named test and there a default page for example index.a5w. If it does not found it Was will throw an error back. So how you bypass this behavior within Alpha5 now? I don't feel confident at all this is possible now.

    If you cheat Was with index.a5w in folder test with redirect then the redirect url has to be a valid url with extension. I don't see anyway to bypass this behavior with Was.

    My conclusion is that url that client sees will always have page extension(and query parameters) with Alpha.

    Leave a comment:


  • frankbicknell
    replied
    Re: Support for URL rewriting under IIS7

    After looking at the rewrite descriptions, Although I don't know the exact procedure I feel confident that you could create your own 'rewrite module' within Alpha5 now.

    Leave a comment:


  • waldhorn
    replied
    Re: Support for URL rewriting under IIS7

    A (belated) update:

    Richard Rabins asked Kurt Rayner to comment on my question. His reply:

    Alpha Five will integrate into the IIS request pipeline as a managed handler. Since the URL Rewrite Module is invoked at the �Begin Request� phase of the pipeline, I don�t anticipate any problems.

    Leave a comment:


  • waldhorn
    replied
    Re: Support for URL rewriting under IIS7

    Thanks for the advice, Keith. I'll give sales a try.

    Cheers,

    Mark

    Leave a comment:


  • Keith Hubert
    replied
    Re: Support for URL rewriting under IIS7

    Hi Mark,

    As this forum is mainly to help with development of applications with the existing releases of Alpha, I suggest you ask your question to [email protected] I'm sure they would pass this to the correct department.

    Leave a comment:


  • waldhorn
    replied
    Re: Support for URL rewriting under IIS7

    Hello, all.

    I posted this question about a week ago.

    Recognizing that the development team doesn't actively monitor each question in the forum, is there a way to elicit a response from development on this question? Some observation about how this an other IIS7-related features will integrate with A5 would be most appreciated.

    Thanks!

    Leave a comment:


  • waldhorn
    started a topic Support for URL rewriting under IIS7

    Support for URL rewriting under IIS7

    Greetings. This is my first post to the Alpha forum. :)

    I'm strongly considering using Alpha Five for internal application development.

    I'm also considering how well it might work as a main public website. Part of the requirements would be the ability to handle URL rewriting. "Pretty URLs" are aesthetically pleasing and are touted as having SEO benefits.

    So, a question for the development team: Will the upcoming Alpha Five IIS integration module support the URL rewrite module under IIS 7 / 7.5?

    Many thanks!
Working...
X