By specifiying this you are only allowing traffic originated from 10.80.122.13 with a source port of 80 and destined to 10.80.9.9 with a destination port of 80. This will normally not work as client browsers initiate a TCP session using a random port number greater than 1024 (ephemeral port range - implentation varies per OS). So while the destination of the packet is still port 80 (as web servers normally are listening on this port) the source port is never 80 (unless specifically requested by the application). So in short, no an http access-list entry should not be specified in the manner you have stated.
Yes,an http port can be opened in this way subjected to host 10.80.9.9 always initiate http connection to 10.80.122.13 on port 80 i.e source port should always be 80 otherwise it won't connect.This you have to specify in the application i.e making the http connection on 10.80.9.9 otherwise don't specify source port and use access-list 110 permit tcp 10.80.122.13 10.80.9.9 eq 80.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...